לא מצליח להיכנס לקונטיינר היישום, אך המערכת עדיין עובדת

סיכום מבוסס בינה מלאכותית

jerdog encountered an error when trying to enter the Discourse app container using ./launcher enter app, receiving a Docker daemon connection error despite the system appearing to run normally. Output from docker info showed Docker version 17.12.0-ce on Ubuntu 16.04, with one running container and no obvious issues. jerdog noted an available Docker upgrade via /admin/docker but hesitated to apply it due to potential downtime (~10 minutes via launcher rebuild). Falco suggested restarting the Docker service. jerdog confirmed the correct command would be sudo systemctl restart docker and, after taking the risk, successfully restarted Docker, resolving the issue jerdog. The fix restored container access without requiring a full rebuild or upgrade.

So was attempting to ./launcher enter app on our production box to check an nginx config setting and getting the following error:

$ ./launcher enter app
/usr/bin/docker: Error response from daemon: connection error: desc = "transport: dial unix /var/run/docker/containerd/docker-containerd.sock: connect: connection refused".
ERRO[0002] error waiting for container: context canceled
Your Docker installation is not working correctly

Everything looks to be running fine on the box but for this…

$ docker info
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 6
Server Version: 17.12.0-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 18
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: N/A (expected: 89623f28b87a6004d4b785663257362d1658a729)
runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f
init version: 949e6fa
Security Options:
apparmor
Kernel Version: 4.4.0-112-generic
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.857GiB
Name: ip-172-31-20-121
ID: 6VH4:WJ6H:T26M:XTUP:QCK2:BLJI:2DYD:YRVS:4AXM:CDPM:QDRC:KFF2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

And for more info, here’s my current version / status:

When I go to /admin/docker I do have an upgrade I could pull in but I don’t want to do that and bring down the whole site since this looks to be having issues at the moment - and a launcher rebuild will take things down for about ~10min

Anyone have any idea here? Worst case I can do a launcher rebuild tonight at low levels of activity…

Did you try restarting the docker service?

is that going to bounce the container? and would I just do a docker restart?

Edit: I would just do sudo systemctl restart docker correct @Falco?

Went ahead and restarted docker - took the chance and it worked. Thanks @Falco