Docker - the open-source application container engine. This chat is intended for contributors new to the Docker project or new to open source. For user help, please goto #docker on freenode. For advanced contributors please goto #docker-dev on freenode.
I am trying to fix this from the last 3 days and not able to fix
Command------ docker run -ti -p 127.0.0.1:5432:5432 -e POSTGRES_HOST_AUTH_METHOD=trust -e LC_COLLATE=en_US.UTF8 -e LC_CTYPE=en_US.UTF8 --rm postgres:11 -c log_statement=all
Error------ docker: Error response from daemon: driver failed programming external connectivity on endpoint trusting_feistel (c76e7077bd6e012a2282670506334a0aef50695489dc20a1992e00e205f0954c): Error starting userland proxy: listen tcp 127.0.0.1:5432: bind: address already in use.
I'm trying to run Docker inside Docker and mounting the /var/run/docker.sock socket
. The socket gets the following permissions and ownership inside the container:
srwxr-xr-x 1 root root 0 Nov 8 17:20 /var/run/docker.sock
meaning it can't be accessed from inside the container with regular user privileges.
What's the best way to resolve this?
WARN[0000] invalid non-bool value for BUILDX_NO_DEFAULT_LOAD:
WARN[0000] No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
[+] Building 6.1s (15/15) FINISHED
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [linux/arm64 internal] load metadata for docker.io/phenompeople/centos-sunjre:JP 6.0s
=> [linux/amd64 internal] load metadata for docker.io/phenompeople/centos-sunjre:JP 6.0s
=> [linux/amd64 1/5] FROM docker.io/phenompeople/centos-sunjre:JP@sha256:b6aa25e541a6102b77fca769738d00027fa3cfd6f2ff15507c4846d3845d7fad 0.0s
=> => resolve docker.io/phenompeople/centos-sunjre:JP@sha256:b6aa25e541a6102b77fca769738d00027fa3cfd6f2ff15507c4846d3845d7fad 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 148B 0.0s
=> [linux/arm64 1/5] FROM docker.io/phenompeople/centos-sunjre:JP@sha256:b6aa25e541a6102b77fca769738d00027fa3cfd6f2ff15507c4846d3845d7fad 0.0s
=> => resolve docker.io/phenompeople/centos-sunjre:JP@sha256:b6aa25e541a6102b77fca769738d00027fa3cfd6f2ff15507c4846d3845d7fad 0.0s
=> CACHED [linux/arm64 2/5] COPY target/test-1.0-SNAPSHOT.jar /opt/deployment/test/test-1.0-SNAPSHOT.jar 0.0s
=> CACHED [linux/arm64 3/5] COPY *-server.sh /opt/deployment/
Haley
But why would one want to run docker under windows. It is slow by default.
Haley
something like that: https://www.learnitguide.net/2020/03/add-new-worker-node-kubernetes-cluster.html
Haley
* You guys got a very simple php-based app, and a docker-compose example yml file for it?
sometimes when I run:
docker stop "$(docker ps --all --quiet)"
docker rm "$(docker ps --all --quiet)"
I get:
Error: No such container: ....
How can docker ps identify a container that doesn't exist? Also, this terminates rm
and causes me to manually rm in order to skip over the container that doesn't exist. Then, when I remove all other containers I am able to remove the one it said didn't exist!
Is there a way to "skip" failed attempts at stopping and removing so that all other containers still get removed?