You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Noteworthy changes from 1.7.1 Distribution Trusted pull, push and build, disabled by default Make tar layers deterministic between registries Don't allow deleting the image of running containers Check if a tag name to load is a valid digest Allow one character repository names Add a more accurate error description for invalid tag name Make build cache ignore mtime Cli Add support for DOCKER_CONFIG
# docker -D -d DEBU[0000] Registering POST, /containers/{name:.*}/unpause DEBU[0000] Registering POST, /containers/{name:.*}/restart DEBU[0000] Registering POST, /exec/{name:.*}/resize DEBU[0000] Registering POST, /containers/create DEBU[0000] Registering POST, /containers/{name:.*}/kill DEBU[0000] Registering POST, /containers/{name:.*}/start DEBU[0000] Registering POST, /containers/{name:.*}/sto
Description of problem: Using -v to bind mount a file into a container does not appear to modify the behavior of lstat or readlink if the target path on the container already exists and is a symbolic link. This causes programs that use these system calls to continue seeing the file present in the container instead of the file on the host system. In our case this caused Java processes to incorrectl
Description Current state of things: Those distros are supported as per http://docs.docker.com/installation/rhel/and http://docs.docker.com/installation/centos/ RedHat themselves only support Docker on RHEL7 (as stated by https://access.redhat.com/solutions/1378023, and confirmed by several people) 1.7.0 is broken on these (most notably because of libnetwork bridge creation code: 1.7.0/CentOS/RHEL
The team behind App Container (appc) is seeking feedback on whether there are any modifications required to the spec to allow it to work natively in Docker. Background App Container (appc) is a specification for running applications in containers. We think App Container represents the next logical iteration in what a container image format, runtime engine, and discovery protocol should look like.
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く