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
Possible values for reschedule are: no: Never reschedule the container (default). on-node-failure: Reschedule the container whenever the node fails. The reason this is more complicated than yes/no is in the future we might have more complicated rescheduling policies (for instance, we might want reschedule containers to re-spread or re-pack them). Open question: Is this really necessary? Rescheduli
Filters tell Docker Swarm scheduler which nodes to use when creating and running a container. Configure the available filters Filters are divided into two categories, node filters and container configuration filters. Node filters operate on characteristics of the Docker host or on the configuration of the Docker daemon. Container configuration filters operate on characteristics of containers, or o
$ export DOCKER_HOST=tcp://leader.me.priv:2375 $ export DOCKER_TLS_VERIFY=1 $ export DOCKER_CERT_PATH=/home/ubuntu/.docker $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES $ docker-compose up -d service ERROR: SSL error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) $ docker-compose version docker-compose version 1.7.0, build 0d7bf73 docker-py version: 1.
Expected behavior Amount of disk space used under ~/Library/Containers/com.docker.docker/ should shrink when deleting images and/or containers Actual behavior Amount of disk space used under ~/Library/Containers/com.docker.docker/ doesn't shrink after deleting ~50 containers and ~141 images (out of a total of 194). My Docker.qcow2 was 41GB both before and after doing these deletions. On the Diagno
*** note *** This only works with Docker Swarm Mode in Docker Engine 1.12.0 and later. It does not work with the separate Docker Swarm project Also this is a sample app meant for learning Docker. Running this app in production is insecure and should be avoided. If you want to run it in production you must take all security precautions, and in particular Protect the Docker daemon socket with SSL. T
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く