GitHub - docker/buildx: Docker CLI plugin for extended build capabilities with BuildKitYou 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
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running? · Issue #4181 · docker/compose
matteo@ubuntuDockerMB:~/wordpress-docker$ sudo docker -v Docker version 1.12.3, build 6b644ec matteo@ubuntuDockerMB:~/wordpress-docker$ sudo docker-compose up ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running? If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable. matteo@ubuntuDockerMB:~/wordpress-docker$ sudo service
File system performance improvements · Issue #1592 · docker/for-mac
Recent Docker versions (17.04 CE Edge onwards) add additional flags to the -v option for docker run that make it possible to specify the consistency requirements for a bind-mounted directory. The flags are consistent: Full consistency. The container runtime and the host maintain an identical view of the mount at all times. This is the default. cached: The host's view of the mount is authoritative.
Support host.docker.internal DNS name to host · Issue #264 · docker/for-linux
This is a bug report This is a feature request I searched existing issues before opening this one Expected behavior As in docker-for-mac and docker-for-windows, inside a container, the DNS name host.docker.internal resolves to an IP address allowing network access to the host (roughly the output of ip -4 route list match 0/0 | cut -d' ' -f3 inside the same container). Actual behavior host.docker.i
docker-compose does not have a way to override tls version at the commandline · Issue #4651 · docker/compose
Using compose, if I set COMPOSE_TLS_VERSION DOCKER_TLS_VERIFY DOCKER_CERT_PATH docker-compose works fine and gives me no errors. If I decide to use command line argument instead of these environment variables, I have no way to set which version of TLS I want to use. For servers that do not support TLS version 1, I get the following errors: ERROR: SSL error: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv
support SSH connection by AkihiroSuda · Pull Request #1014 · docker/cli
Signed-off-by: Akihiro Suda suda.akihiro@lab.ntt.co.jp - What I did Added support for SSH connection. e.g. docker -H ssh://me@server - How I did it Followed @tonistiigi 's suggestion: #889 (comment) The cli should accept ssh://me@server for DOCKER_HOST and -H. Using that would execute ssh with the passed config. The ssh command would call a hidden command on the docker CLI binary on the remote sid
Unable to docker login through CLI - unauthorized: incorrect username or password · Issue #935 · docker/hub-feedback
using CLI I am unable to login. docker login Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one. Username: USERNAME@gmail.com Password: Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password OS MAC docker version Client: Version: 1.13.0 API versio
docker login returns "error getting credentials - err: exit status 1 ..." · Issue #60 · docker/docker-credential-helpers
The docker login command is returning the following error for two users out of three users on the same physical host using docker-credential-secretservice Release v0.5.0. The user that can login to docker hub does not have any issue pushing or pulling. All users have the same docker environment variable settings, path, file permissions and content for $HOME/.docker/config.json, run the same shell
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Compose error "HTTP request took too long to complete" · Issue #3633 · docker/compose
The input device is not a TTY · Issue #5696 · docker/compose
docker: Error response from daemon: Get https://registry-1.docker.io/v2/library/hello-world/manifests/latest: unauthorized: incorrect username or password. · Issue #2640 · docker/for-mac
docker login fails while docker-compose is installed on Ubuntu 18.04 · Issue #6023 · docker/compose
GitHub - docker/for-aws
docker-compose run/exec converts unix newlines to CRLF · Issue #4550 · docker/compose
18.09: containerd depends on overlay · Issue #475 · docker/for-linux
two-factor authentication · Issue #358 · docker/hub-feedback
default-address-pools can not be specified in configuration · Issue #3108 · docker/for-mac
GitHub - docker/docker-ce: Docker CE
Scale a container specifying ports · Issue #1241 · docker/compose
GitHub - docker/cli: The Docker CLI
