# 无法进入应用容器，仍然在运行

**URL:** https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236
**Category:** Self-hosting
**Created:** [2018年三月5日 16:41 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236 "2018-03-05T16:41:30Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)
#### Post date: [2018年三月5日 16:41 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/1 "2018-03-05T16:41:30Z")

</div>

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/](https://index.docker.io/v1/)  
> Labels:  
> Experimental: false  
> Insecure Registries:  
> 127.0.0.0/8  
> Live Restore Enabled: false
> 
> WARNING: No swap limit support

---

<div class="post-metadata">

### Author: ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)
#### Post date: [2018年三月5日 17:02 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/2 "2018-03-05T17:02:38Z")

</div>

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

 ![image](https://global.discourse-cdn.com/meta/original/3X/2/a/2ac62d45865726313252842eb3dcac461b262e42.png)

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

---

<div class="post-metadata">

### Author: ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)
#### Post date: [2018年三月5日 18:46 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/3 "2018-03-05T18:46:48Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2018年三月5日 18:49 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/4 "2018-03-05T18:49:17Z")

</div>

Did you try restarting the docker service?

---

<div class="post-metadata">

### Author: ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)
#### Post date: [2018年三月5日 18:53 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/5 "2018-03-05T18:53:16Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)
#### Post date: [2018年三月5日 20:59 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/6 "2018-03-05T20:59:46Z")

</div>

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

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2024年六月8日 12:37 UTC](https://meta.discourse.org/t/cant-enter-app-container-still-working-though/82236/7 "2024-06-08T12:37:47Z")

</div>

此主题已在 2286 天后自动关闭。不再允许回复。
