Sometimes a docker container gets stuck so that it can't be stopped or removed

CONTAINER ID        IMAGE                            COMMAND                CREATED             STATUS              PORTS                                                NAMES
1fb364265a92        mediit/mongodb:stage             "mongod"               22 minutes ago      Up 22 minutes       <IP_ADDRESS>:49195->27017/tcp, <IP_ADDRESS>:49196->28017/tcp   mongodb

$ docker stop mongodb
Error response from daemon: Cannot stop container mongodb: no such process
FATA[0000] Error: failed to stop one or more containers

$ docker rm -f mongodb
Error response from daemon: Could not kill running container, cannot remove - no such process
FATA[0001] Error: failed to remove one or more containers

$ docker info
Containers: 14
Images: 178
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 206
Execution Driver: native-0.2
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 2
Total Memory: 7.704 GiB
Name: medi-it-sote
ID: GGAU:OQIH:U6ZI:TOEP:G3JX:Z5WA:D5WQ:CFPA:NLMB:F6P5:IR7I:2GTC
WARNING: No swap limit support

$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

$ uname -a
Linux medi-it-sote 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

This happens occasionally, any ideas?

@deiga Please provide full output of docker info, docker version and uname -a. There's no way to help without this information. Please provide these bits of information when reporting an issue or commenting on an issue reported by someone else to say you're also running into the same problem.

@unclejack Yes, of course. I updated the original question with the information you asked for

#10528 . Same problem.

+1

+1

It is fixed in docker 1.5 version.

is anyone else in this thread using 1.5

Thanks for the feedback. We will update to 1.5.

so I am going to close this, BUT if you see it still on 1.5 ping me to reopen

I have what appears to be a zombie container - it can't be stopped, killed, rmed, or rm -fed.
core@localhost ~ $ docker info
Containers: 4
Images: 141
Storage Driver: overlay
Backing Filesystem: extfs
Execution Driver: native-0.2
Kernel Version: 3.19.0
Operating System: CoreOS 612.1.0
CPUs: 1
Total Memory: 998 MiB
core@localhost ~ $ docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.3.3
Git commit (client): a8a31ef-dirty
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.3.3
Git commit (server): a8a31ef-dirty
core@localhost ~ $ uname -a
Linux localhost 3.19.0 #2 SMP Fri Mar 6 00:23:51 UTC 2015 x86_64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz GenuineIntel GNU/Linux

Found a couple of clues.
After rebooting the VM, the container can be removed.
The issue is reproducible on my system. I can share my Dockerfile if needed, but here's the gist: OS X host, CoreOS VM managed by Vagrant as docker host, base image is dockerfile/ubuntu:latest. I'm mounting a volume into the container (using Vagrant's NFS mount), and then doing an npm install. The container freezes up part way through the install process - I can't ctrl+c the install, can't stop the container, or even docker exec a new shell into it.

Issue still exists on v1.7

There is more info about this in #12738.

I'm also experiencing this problem.
Host: Arch Linux (amd64), using Vagrant with CoreOS & NFS
Any plans to solve this? Are there any known solutions?

Same problem debian jessie x64
docker --version
Docker version 1.6.2, build 7c8fca2
============================
docker ps -a
CONTAINER ID        IMAGE                                                                     COMMAND             CREATED             STATUS                      PORTS               NAMES
f1bea984deae        8eb20e13c4d8b82408c60eccea35bea0d5e99a224f0d6065b33b819c7e777a26:latest   "-exec /bin/bash"   12 minutes ago
docker stop f1bea984deae
f1bea984deae
docker rmi 8eb20e13c4d8b82408c60eccea35bea0d5e99a224f0d6065b33b819c7e777a26
Error response from daemon: Conflict, cannot delete 8eb20e13c4d8 because the container f1bea984deae is using it, use -f to force
FATA[0000] Error: failed to remove one or more images

Removal In Progress for more than an hour :(

Same (running containers off the official cassandra image):
Containers: 3
Images: 13
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 19
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.13-boot2docker
Operating System: Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: 323I:I66I:JYQC:XBC6:K5OO:5VH2:EQ23:3YCL:WWOX:IUJ4:ECBY:6RUX
Debug mode (server): true
 File Descriptors: 39
 Goroutines: 103
 System Time: 2015-11-21T06:35:22.202794522Z
 EventsListeners: 1
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.5.1
 Git commit:   a34a1d5
 Built:        Sat Nov 21 00:49:19 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

Darwin Soma.nc.rr.com 15.0.0 Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64

I had similar problem trying to run then exit out or or kill sequenceiq/spark:1.5.1. Once I increased the memory of the VM from 2GB to 3GB everything worked fine.

@neverfox exactly the same problem here, with the same image +1

Same issue with our own Cassandra 2.1.11 image (based on ubuntu:14.04).  It seems that something is causing it shutdown (we are surely not asking it to shutdown) and then hanging in the process of that.  Here's the end of docker logs ...:

Same issue with the official icinga/icinga2 image. The only way to stop the container was to reboot the machine.

Same issue here with a simple nginx container running rails (Docker 1.9.1)

We had the same issue. It seemed to have occurred when the server's kernel was upgraded to 3.13.0-73.116.
We reverted the kernel to 3.13.0-71.114, which seems to have fixed the problem for us.

Experience the problem with Docker 1.9.1 and Linux 3.13.0-74
Other identical load with older Linux (3.13.0-24-generic) does not seem to have this problem

Is there a new issue for this since this one is closed and no one from Docker, Inc seems to be following it?

Same issue. Arose immediately when upgrading to docker 1.9 (via toolbox) on OSX. In this case, the container is a centos-base with a simple, self contained mongodb install. The process tries to exit but gets stuck.
$ docker logs mongodb /usr/bin/mongod --help for help and startup options 2016-01-07T23:49:52.204+0000 [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=2f4e5cf01260 2016-01-07T23:49:52.211+0000 [initandlisten] db version v2.6.11 2016-01-07T23:49:52.211+0000 [initandlisten] git version: nogitversion 2016-01-07T23:49:52.211+0000 [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013 2016-01-07T23:49:52.211+0000 [initandlisten] build info: Linux buildvm-08.phx2.fedoraproject.org 4.1.4-100.fc21.x86_64 #1 SMP Tue Aug 4 03:25:05 UTC 2015 x86_64 BOOST_LIB_VERSION=1_53 2016-01-07T23:49:52.211+0000 [initandlisten] allocator: tcmalloc 2016-01-07T23:49:52.211+0000 [initandlisten] options: {} 2016-01-07T23:49:52.217+0000 [initandlisten] journal dir=/data/db/journal 2016-01-07T23:49:52.218+0000 [initandlisten] recover : no journal files present, no recovery needed 2016-01-07T23:49:52.312+0000 [initandlisten] allocating new ns file /data/db/local.ns, filling with zeroes... 2016-01-07T23:49:52.350+0000 [FileAllocator] allocating new datafile /data/db/local.0, filling with zeroes... 2016-01-07T23:49:52.350+0000 [FileAllocator] creating directory /data/db/_tmp 2016-01-07T23:49:52.351+0000 [FileAllocator] done allocating datafile /data/db/local.0, size: 64MB,  took 0 secs 2016-01-07T23:49:52.352+0000 [initandlisten] build index on: local.startup_log properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "local.startup_log" } 2016-01-07T23:49:52.352+0000 [initandlisten] 	 added index to empty collection 2016-01-07T23:49:52.352+0000 [initandlisten] waiting for connections on port 27017 2016-01-07T23:50:02.866+0000 [initandlisten] connection accepted from <IP_ADDRESS>:55312 #1 (1 connection now open) 2016-01-07T23:50:04.885+0000 [initandlisten] connection accepted from <IP_ADDRESS>:55331 #2 (2 connections now open) 2016-01-07T23:50:04.889+0000 [initandlisten] connection accepted from <IP_ADDRESS>:55332 #3 (3 connections now open) 2016-01-07T23:50:04.906+0000 [conn2] allocating new ns file /data/db/logstream.ns, filling with zeroes... 2016-01-07T23:50:04.913+0000 [initandlisten] connection accepted from <IP_ADDRESS>:55333 #4 (4 connections now open) 2016-01-07T23:50:04.970+0000 [FileAllocator] allocating new datafile /data/db/logstream.0, filling with zeroes... 2016-01-07T23:50:04.970+0000 [FileAllocator] done allocating datafile /data/db/logstream.0, size: 64MB,  took 0 secs 2016-01-07T23:50:04.971+0000 [conn2] build index on: logstream.documents properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "logstream.documents" } 2016-01-07T23:50:04.971+0000 [conn2] 	 added index to empty collection 2016-01-07T23:50:50.767+0000 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends 2016-01-07T23:50:50.767+0000 [signalProcessingThread] now exiting 2016-01-07T23:50:50.767+0000 [signalProcessingThread] dbexit:  2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: going to close listening sockets... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] closing listening socket: 7 2016-01-07T23:50:50.767+0000 [signalProcessingThread] closing listening socket: 8 2016-01-07T23:50:50.767+0000 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: going to flush diaglog... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: going to close sockets... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: waiting for fs preallocator... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: lock for final commit... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: final commit... 2016-01-07T23:50:50.767+0000 [conn3] end connection <IP_ADDRESS>:55332 (3 connections now open) 2016-01-07T23:50:50.767+0000 [conn4] end connection <IP_ADDRESS>:55333 (3 connections now open) 2016-01-07T23:50:50.767+0000 [conn1] end connection <IP_ADDRESS>:55312 (3 connections now open) 2016-01-07T23:50:50.767+0000 [conn2] end connection <IP_ADDRESS>:55331 (3 connections now open) 2016-01-07T23:50:50.767+0000 [signalProcessingThread] shutdown: closing all files... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] closeAllFiles() finished 2016-01-07T23:50:50.767+0000 [signalProcessingThread] journalCleanup... 2016-01-07T23:50:50.767+0000 [signalProcessingThread] removeJournalFiles 2016-01-07T23:50:50.768+0000 [signalProcessingThread] shutdown: removing fs lock... 2016-01-07T23:50:50.768+0000 [signalProcessingThread] dbexit: really exiting now $ docker ps CONTAINER ID        IMAGE                                          COMMAND             CREATED             STATUS              PORTS               NAMES 2f4e5cf01260        mongodb:dev-snapshot   "/usr/bin/mongod"   4 minutes ago       Up 4 minutes        27017/tcp           mongodb $ docker rm -f mongodb (hangs)

Same here, a container got stuck during execution, and now cannot remove it neither stop it (even with option -f).
Output of docker info
Containers: 20
Images: 1015
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1055
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-66-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 3.86 GiB
Name: vagrant-ubuntu-trusty-64
ID: WLJM:DQX6:A6O2:CHGD:VN6O:Y72K:HTEU:JAZG:I7C2:FLVQ:V26J:7XEF
Username: bitliner
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Output of docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

I don't know if it is related, but dmesg's output contains a lot of following entries
type=1400 audit(1452275709.969:7731): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=9530 comm="chrome" requested_mask="trace" denied_mask="trace" peer="docker-default"

it looks like apparmor is denying to kill that process

This issue seems to be closed. Any new one to follow this up? I am having the same problem.

This solved the issue for me (until it is fixed in the kernel): https://github.com/docker/docker/issues/18180#issuecomment-167042078

Based on the upper link from @obeattie (thanks!) - I switched the storage driver to overlay.
I'm using Ubuntu 14.04.
For me switching to overlay solved the issue:
In /etc/default/docker
DOCKER_OPTS="--storage-driver=overlay"

@klodoma I'm copying my comment from #18180 here warning that OverlayFS is not always a safe choice workaround.
Note for others that switching to OverlayFS requires kernel version 3.18+ on Linux, and as quoted on Docker's page, As promising as OverlayFS is, it is still relatively young. Therefore caution should be taken before using it in production Docker environments., and, comes with a warning that turning on OverlayFS should be preceded by effectively backing up any images you might have by pushing them all to a registry beforehand.

@mikeatlas Thanks. I'll give it a try by downgrading.

@mikeatlas @klodoma I think Docker version doesn't matter. I suggest downgrading the kernel.
(If you are using Boot2Docker, downgrading Boot2Docker to 1.8.3 makes a sense, because it also downgrades the kernel.)

Yeah, having done both I suppose I am not scientifically isolating my workaround fix on my Ubuntu box...
Nice work on getting the boot2docker patch @AkihiroSuda !!! - now... how long to wait for linux kernel patch?

@mikeatlas It's ready:smile: : boot2docker/boot2docker#1113
I think the patch will be also applied to major distros soon.

@AkihiroSuda  What version should we downgrade to if we want to use docker networking and be able to kill broken containers?

@JoachimAndersson Boot2Docker v1.9.0 should work. Or you can build the latest Boot2Docker manually.

worth knowing - if you are running an ENTRYPOINT script ... the script will work with the shebang #!/bin/bash -x BUT will stop the container from stopping with #!/bin/bash -xe
hope that helps someone

if you're feeling adventurous, there's a boot2docker 1.10.0-rc1 release candidate as well; https://github.com/tianon/boot2docker-legacy/releases

@thaJeztah it wasn't obvious to me based on your comment, but the 1.10.0-rc1 boot2docker.iso will not work with the existing stable docker 1.9.1 client:
docker pull my/package
Error response from daemon: unsupported manifest mediatype: text/html; charset=utf-8

You'd have to do a full upgrade of all things docker.
However, using the 1.9.0 release boot2docker.iso has solved this problem for me.

@lhazlewood are you using a private registry, or is that from docker hub?

I encountered the problem with boot2docker 1.9.x with a custom mongodb container. I use docker machine in combination with VMware vSphere. When i set 2 cpus the problem still occured most of the time (about 90% of the times i tried to stop the container).
Boot2Docker 1.10.0-rc1 actually seems to solve the problem in my case and i can stop the mongodb container. Thanks to @tianon !

@thaJeztah I was using a private registry.

@lhazlewood yes, looks like some registries (or older versions of the registry) don't return the right content-type. Docker uses the content-type to apply the right manifest-type. However, we made this check more tolerant, and now accept those content-types; see https://github.com/docker/docker/pull/19552. We're building / pushing docker 1.10-RC2 while we speak, so you should be able to get a fix for that soon

Much appreciated!
FWIW, if it helps, we use Artifactory to retain all private engineering build assets, including Docker images.  (I am not affiliated w/ Artifactory in any way - just a happy user).

@lhazlewood thanks! I think Artifactory is working on being better compliant to the standard, but for now, this works :)

Ping @jfrazelle you said to ping you to possibly re-open this issue if someone saw this problem again. Well it seems like a lot of people have been seeing it since 1.5 and I'm currently seeing it on 1.10.
Could you please re-open this issue?
This is all I can see in my log:
INFO[67974] Container c57136420ed3 failed to exit within 10 seconds of kill - trying direct SIGKILL

@rbjorklin does it get killed after that? "failed to exit within 10 seconds" could be an indication that the containers PID 1 doesn't handle signals properly

@thaJeztah No it remains indefinitely no matter what I do. None of stop/kill/rm -f makes any difference.

@rbjorklin just to narrow down possibilities; are you using aufs, and does the container process take up 100% cpu (thinking of https://github.com/docker/docker/issues/18180)

Thanks @thaJeztah looks like #18180 is the problem I'm seeing!

+1

@rbjorklin ah, right. In that case; the discussion on that thread contains a lot of information; depending on the distro you're running on, the kernel may not have been patched yet, so you may need a workaround in the meantime.

+1

+1 (Docker version 1.10.2, build c3959b1)

@coftysweet Have you checked out the issue that @thaJeztah mentioned? If you're using AUFS then that's most likely the problem you're seeing. You can check it with:
docker info | grep Storage

same here, docker cannot rm, stop or kill the container.
➜  app git:(master) ✗ docker info
Containers: 91
 Running: 2
 Paused: 0
 Stopped: 89
Images: 296
Server Version: 1.10.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 490
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.19.0-49-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.844 GiB
Name: ubuntu
ID: 2HH2:BL4I:ZPYE:BIXT:656Y:R7FQ:I6RQ:7H7U:YHLI:BO6K:TY2Z:6FGB
WARNING: No swap limit support

➜  app git:(master) ✗ docker logs zleek-neo4j
Starting Neo4j Server...process [139]... waiting for server to be ready............ OK.
http://localhost:7474/ is ready.
Stopping Neo4j Server [139].... done
Starting Neo4j Server console-mode...
2016-03-03 21:48:25.629+0000 INFO  Successfully started database
2016-03-03 21:48:25.719+0000 INFO  Starting HTTP on port 7474 (4 threads available)
2016-03-03 21:48:26.301+0000 INFO  Enabling HTTPS on port 7473
2016-03-03 21:48:26.510+0000 INFO  Mounting static content at /webadmin                                                                [22/1813]
2016-03-03 21:48:26.711+0000 INFO  Mounting static content at /browser
2016-03-03 21:48:29.938+0000 INFO  Remote interface ready and available at http://<IP_ADDRESS>:7474/
2016-03-03 21:59:29.931+0000 INFO  Neo4j Server shutdown initiated by request
2016-03-03 21:59:30.035+0000 INFO  Successfully shutdown Neo4j Server
2016-03-03 21:59:30.125+0000 INFO  Successfully stopped database
2016-03-03 21:59:30.126+0000 INFO  Successfully shutdown database
Starting Neo4j Server...process [142]... waiting for server to be ready........... OK.
http://localhost:7474/ is ready.
Stopping Neo4j Server [142].... done
Starting Neo4j Server console-mode...
2016-03-03 22:02:14.884+0000 INFO  Successfully started database
2016-03-03 22:02:14.927+0000 INFO  Starting HTTP on port 7474 (4 threads available)
2016-03-03 22:02:15.295+0000 INFO  Enabling HTTPS on port 7473
2016-03-03 22:02:15.431+0000 INFO  Mounting static content at /webadmin
2016-03-03 22:02:15.529+0000 INFO  Mounting static content at /browser
2016-03-03 22:02:17.219+0000 INFO  Remote interface ready and available at http://<IP_ADDRESS>:7474/
Starting Neo4j Server...process [141]... waiting for server to be ready.................. OK.
http://localhost:7474/ is ready.
Stopping Neo4j Server [141].... done
Starting Neo4j Server console-mode...
2016-03-04 14:17:36.572+0000 INFO  Successfully started database
2016-03-04 14:17:36.611+0000 INFO  Starting HTTP on port 7474 (4 threads available)                                                     [0/1813]
2016-03-04 14:17:37.014+0000 INFO  Enabling HTTPS on port 7473
2016-03-04 14:17:37.133+0000 INFO  Mounting static content at /webadmin
2016-03-04 14:17:37.209+0000 INFO  Mounting static content at /browser
2016-03-04 14:17:38.582+0000 INFO  Remote interface ready and available at http://<IP_ADDRESS>:7474/
2016-03-04 14:24:48.444+0000 INFO  Neo4j Server shutdown initiated by request
2016-03-04 14:24:48.519+0000 INFO  Successfully shutdown Neo4j Server
2016-03-04 14:24:48.592+0000 INFO  Successfully stopped database
2016-03-04 14:24:48.592+0000 INFO  Successfully shutdown database
Starting Neo4j Server...process [141]... waiting for server to be ready.......... OK.
http://localhost:7474/ is ready.
Stopping Neo4j Server [141].... done
Starting Neo4j Server console-mode...
2016-03-04 14:25:42.498+0000 INFO  Successfully started database
2016-03-04 14:25:42.541+0000 INFO  Starting HTTP on port 7474 (4 threads available)
2016-03-04 14:25:42.916+0000 INFO  Enabling HTTPS on port 7473
2016-03-04 14:25:43.043+0000 INFO  Mounting static content at /webadmin
2016-03-04 14:25:43.126+0000 INFO  Mounting static content at /browser
2016-03-04 14:25:44.578+0000 INFO  Remote interface ready and available at http://<IP_ADDRESS>:7474/
2016-03-04 14:30:23.639+0000 INFO  Neo4j Server shutdown initiated by request
2016-03-04 14:30:23.688+0000 INFO  Successfully shutdown Neo4j Server
2016-03-04 14:30:23.763+0000 INFO  Successfully stopped database
2016-03-04 14:30:23.763+0000 INFO  Successfully shutdown database

➜  app git:(master) ✗ docker --version
Docker version 1.10.2, build c3959b1

➜  app git:(master) ✗ uname -a
Linux ubuntu 3.19.0-49-generic #55~14.04.1-Ubuntu SMP Fri Jan 22 11:24:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

@tugberkugurlu have you checked if https://github.com/docker/docker/issues/18180 is your issue?

FWIW, I too had been seeing similar problems, and I too resolved them by upgrading the kernel, following the advice provided in #18180.
I suspect a kernel upgrade will solve your problem too, @tugberkugurlu.

1 Docker version 1.10.2, build c3959b1

Docker version 1.9.1, build a34a1d5 kernel 4.2.0-23-generic
Same here. Cannot kill/stop/rm a container.

+1

Seeing the same thing here.
$ sudo docker info
Containers: 2
Images: 55
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 59
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-74-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 2
Total Memory: 3.676 GiB
Name: ip-172-31-3-155
ID: O56Q:6A3D:SXDH:BKGX:JSWV:ZKE4:GPZF:D6OR:QDKQ:7R76:ZDZX:PU7C
Username: bshlgrs
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

$ sudo docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

@bshlgrs Looks like #18180.
Kernel 3.13.0-79.123 or later should work．

@AkihiroSuda  That indeed works, thanks

I seem to have kernel 3.19.0-49-generic but still having this issue for neo4j/neo4j:2.3.2 image from official docker registry.
➜  ~ docker info
Containers: 6
 Running: 1
 Paused: 0
 Stopped: 5
Images: 69
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 155
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.19.0-49-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.844 GiB
Name: ubuntu
ID: 2HH2:BL4I:ZPYE:BIXT:656Y:R7FQ:I6RQ:7H7U:YHLI:BO6K:TY2Z:6FGB
WARNING: No swap limit support

It is stuck and docker-compose stop gives below info:
➜  foo git:(master) ✗ docker-compose stop
Stopping foo-neo4j ...

ERROR: for foo-neo4j  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=70)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

docker kill {container-id} also doesn't work.

Having the same issue on 3.19.0-42-generic with mongo:2.4
$ docker info
Containers: 4
 Running: 1
 Paused: 0
 Stopped: 3
Images: 45
Server Version: 1.11.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 77
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.19.0-42-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 62.69 GiB
Name: XXXX
ID: ZSPM:MSAP:Z4EK:CX4F:KRWL:XUVH:HEKQ:ZUOW:JZLB:PVT4:Y3J3:NZ5V
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

ERROR: for appjob1_mongo_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=70)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

@jfrazelle can this be reopened as it seems that it's still happening for some certain cases?

@tugberkugurlu could you open a new issue? Browsing through this issue, it's becoming a collection of unrelated issues, with the same (or similar) symptoms, so I'd rather have a new issue

@thaJeztah https://github.com/docker/docker/issues/22357, thx!

Same problem here with docker 1.11.0, Fedora 23, kernel 4.2.3. I have to restart docker service, so I can remove the stuck container.

Same issue using docker-machine with docker 1.10.3 on OSX. Restarting the machine instance does not fix. I'm probably going to have to kill the machine and create a new one.

docker ps --all
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                PORTS               NAMES
9adaaacc30d3        3d93fd21072f        "/bin/bash"         12 weeks ago        Removal In Progress                       9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_9adaaacc30_web

+1
zhechen@zhechen-ThinkPad-E450:~/commit/postmanc$ docker ps -a | grep postman-dev-com
2b6ec6887c71        docker-repo.corp.cootek.com:5000/postman-dev:1.0             "/bin/bash"              3 weeks ago         Removal In Progress                           postman-dev-com
zhechen@zhechen-ThinkPad-E450:~/commit/postmanc$ docker info
Containers: 71
Running: 6
Paused: 0
Stopped: 65
Images: 147
Server Version: 1.11.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 290
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 3.16.0-70-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.712 GiB
Name: zhechen-ThinkPad-E450
ID: XAHI:S7VD:L5IR:NA2Q:FSOJ:Q5G5:EJUH:7YPI:Q7RV:ZXWI:DUL5:JZFP
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

+1
xxx@xxx-ThinkPad-E450:~/commit/postmanc$ docker ps -a | grep postman-dev-com
2b6ec6887c71        docker-repo.corp.cootek.com:5000/postman-dev:1.0             "/bin/bash"              3 weeks ago         Removal In Progress                           postman-dev-com
xxx@xxx-ThinkPad-E450:~/commit/postmanc$ docker info
Containers: 71
Running: 6
Paused: 0
Stopped: 65
Images: 147
Server Version: 1.11.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 290
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 3.16.0-70-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.712 GiB
Name: zhechen-ThinkPad-E450
ID: XAHI:S7VD:L5IR:NA2Q:FSOJ:Q5G5:EJUH:7YPI:Q7RV:ZXWI:DUL5:JZFP
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Same problem here. Problem still persist.
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Wed Apr 27 00:34:20 2016
OS/Arch:      linux/amd64
Server:
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Wed Apr 27 00:34:20 2016
OS/Arch:      linux/amd64

Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 3
Server Version: 1.11.1
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 46
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.4.8-boot2docker
Operating System: Boot2Docker 1.11.1 (TCL 7.0); HEAD : 7954f54 - Wed Apr 27 16:36:45 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.858 GiB
Name: default
ID: VTLG:L5OC:SF3Q:IZTA:FKDQ:VRU5:SIIG:H7ZL:DFXT:EPAF:4Z7A:T7PV
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug mode (client): false
Debug mode (server): true
File Descriptors: 16
Goroutines: 33
System Time: 2016-05-13T10:51:07.033358043Z
EventsListeners: 0
Username: beckend
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox

only sudo /etc/init.d/docker restart helps or docker-machine restart default, for those in trouble here ;)

+1 same thing for me
root@ci:~# docker ps -a | grep drone:latest
d8410ad0ce6f        drone/drone:latest                 "/drone serve"            44 hours ago        Up 44 hours                   8000/tcp, <IP_ADDRESS>:443->8443/tcp   drone-to-remove
c43f579838ff        drone/drone:latest                 "/drone serve"            2 weeks ago         Removal In Progress                                             drone

Containers: 482
 Running: 15
 Paused: 0
 Stopped: 467
Images: 822
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1798
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.4.0-22-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.33 GiB
Name: ci.dimelo.com
ID: BDWC:L7F2:CHYI:3E6N:F2NA:IKGO:5SRV:CWQF:EQWH:ES4S:DKYK:4L4T
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Username: dimelo
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

I can reproduce the issue by mounting a symlink not reachable for docker into an image.

@DanielSiepmann could you open a new issue for that, and the steps to reproduce?

Same for me. Docker 1.11.1 / Boot to docker 1.11.1.
$ docker info
Containers: 11
 Running: 6
 Paused: 0
 Stopped: 5
Images: 14
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 116
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: weave null host weavemesh bridge
Kernel Version: 4.4.8-boot2docker
Operating System: Boot2Docker 1.11.1 (TCL 7.0); HEAD : 7954f54 - Wed Apr 27 16:36:45 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: swarm-master
ID: 7QGM:6XSO:JMQP:RA4C:6VH4:WFWV:M5LB:TPB5:D27R:7FHY:CZJZ:VBC3
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 72
 Goroutines: 146
 System Time: 2016-05-30T10:45:21.72414025Z
 EventsListeners: 4
Username: philwinder
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Cluster store: consul://<IP_ADDRESS>:8500
Cluster advertise: <IP_ADDRESS>:2376

$ docker-machine version
docker-machine version 0.7.0, build a650a40

Seems to be the same as:
https://github.com/docker/docker/issues/22312
Which has a PR merged. So fingers crossed for next release.
In the mean time, I found that stopping the docker daemon, then manually deleting the container folders allowed me to continue without destroying the vm. E.g.
$ sudo /etc/init.d/docker stop
$ sudo ls /var/lib/docker/containers
05aee7dfa27a3501d0fce4397a8c457327987ab42560377c05fe4a0d9cc47c12  aa29a5fdb4d5925d3bc83dabdf1009495ae3a919c515cf1e21e5752bcced0277
...
sudo rm -r /var/lib/docker/containers/5c25b81e541fef4fbaee89debe3bc812f1db57848977ec41fd9261191d47e708
...etc...
sudo /etc/init.d/docker start

Docker version 1.11.1, Kernel Version: 4.2.0-27-generic
Same here. Cannot kill/stop/rm a container.

Same here, I neither stop the docker service, nor run docker info. It seems all docker commands suck.

@jfrazelle Please re-open this. Still  happen in 1.10.3

@polyrabbit, It will be good if you use ps -ef or pstree to track the ps tree, and find out which process is stuck.
BTW, as I know the best solution to debug a hang issue is to print all the backtrace of goroutines, just like "thread apply all bt" in gdb. There is a custom-gdb python script for print all goroutines. However, I cannot  disable optimization for docker. I opened an issue of https://github.com/docker/docker/issues/24206.

same here
docker info
Containers: 5
 Running: 2
 Paused: 0
 Stopped: 3
Images: 200
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /mnt/docker/aufs
 Backing Filesystem: extfs
 Dirs: 188
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.13.0-77-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.859 GiB
Name: ip-172-31-24-186
ID: VM2F:7T2S:UN43:2WGY:UZSC:3SVT:F4AE:MD4K:BRTU:QHV7:OXDL:2LSJ
Docker Root Dir: /mnt/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

+1
docker info
Containers: 7  Running: 7  Paused: 0  Stopped: 0 Images: 23 Server Version: 1.11.2 Storage Driver: aufs  Root Dir: /var/lib/docker/aufs  Backing Filesystem: extfs  Dirs: 101  Dirperm1 Supported: false Logging Driver: json-file Cgroup Driver: cgroupfs Plugins:   Volume: local  Network: null host bridge Kernel Version: 3.13.0-74-generic Operating System: Ubuntu 14.04.3 LTS OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.305 GiB Name: ip-10-1-5-207 ID: HOHD:CZFW:UNEW:XXMQ:WDGI:ZXWD:CML7:OFCJ:GLXX:VAKM:GXPB:MS5B Docker Root Dir: /var/lib/docker Debug mode (client): false Debug mode (server): false Username: mgolionko Registry: https://index.docker.io/v1/ WARNING: No swap limit support
uname -r
3.13.0-74-generic

+1 still happens.
docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-31-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.503 GiB
Name: mkn8rd-ThinkPad-T550
ID: WXPQ:FO3K:YI6P:CF66:R3CI:57G5:CCGO:M7OP:DMPV:CFN3:LM5I:62NH
WARNING: No swap limit support

docker --version
Docker version 1.10.3, build 20f81dd

This workaround helped me.

@mkn8rd the issue you linked to mentions will be fixed in docker 1.12 (and is a different issue from this one); are you still able to reproduce your issue on the docker 1.12 release candidates? https://github.com/docker/docker/releases (if you have a machine to test on)

Not sure if this is the same issue as docker stop fails sporadically, leaving a zombie container that can't be stopped. It is not stuck in a "Removal in Progress" state but is seen as running. All other commands work as expected AFAICT.
# docker info
Containers: 46
 Running: 46
 Paused: 0
 Stopped: 0
Images: 19
Server Version: 1.11.2
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.13-040413-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 120.1 GiB
Name: ip-10-97-0-79
ID: QN3M:KLBY:VSIN:GYJZ:FMIM:JPOX:OYGK:6AP5:QUE4:U5SI:7EYL:6C4U
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 252
 Goroutines: 606
 System Time: 2016-07-19T13:29:09.605271445Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/

# docker top 1b302f8fa6f6ec6fde0de34fa8baa93db0cf473ca315861afca372a462936b5d
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
10002               65720               61099               0                   Jul18               ?                   00:00:03            [java] <defunct>

# ls /var/lib/docker/overlay/1b302f8fa6f6ec6fde0de34fa8baa93db0cf473ca315861afca372a462936b5d
ls: cannot access /var/lib/docker/overlay/1b302f8fa6f6ec6fde0de34fa8baa93db0cf473ca315861afca372a462936b5d: No such file or directory

# docker ps --no-trunc | grep 1b302f8fa6f6
1b302f8fa6f6ec6fde0de34fa8baa93db0cf473ca315861afca372a462936b5d   matlab_online/worker-with-mdcsserver   "/sbin/my_init"     16 hours ago        Up 16 hours         <IP_ADDRESS>:8011->8080/tcp, <IP_ADDRESS>:10011->8888/tcp   angry_kirch_11
```

Having this issue every once in a while with Docker For Mac beta, Docker version 1.12.0-rc4, build e4a0dbc, experimental.
Zombie containers refuse to take in any commands (stop, rm...), but restarting Docker For Mac and retrying helps after getting few of these kinds of messages (assuming that something is still booting up?)
An error occurred trying to connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/foo-container/stop?t=10: EOF

...

Error response from daemon: Bad response from Docker engine

I think we should make sure whether the issue is 'hang' or 'fail'.
If it's a hang issue:
Identify the hang position (most likely is hang in daemon), so 'kill -SIGUSR1 <daemon_pid>'and then pasting the goroutines' stacktrace will be helpful. Sometimes it may stuck in kernel, so should get all the kernel thread info by 'echo t > /proc/sysrq-triger'.
If it's a failure issue:
I also met the same issue. The PID is stored in memory, but the process already disappeared.

I am experiencing this issue once out of two times under 4.2.0-27-generic #32~14.04.1-Ubuntu. It could never be reproduced under Docker for Mac which I find quite interesting, may point to Ubuntu. Both builds are like below.
Version:      1.12.0
API version:  1.24
Go version:   go1.6.3
Git commit:   8eab29e

Hi guys, just figure out what's happening on my side, in my case, I have a mounted volume delete before restarting the container, but there is no error for the missing volume, and after reboot instance the container will successfully boot up (with --restart=always), it will create the missing volume directory it self, that cause me can't find what really cause this problem.

Cc @tonistiigi: PTAL.

I think we should close this. Like @thaJeztah said, this is a collection of unrelated problems. There are people commenting with their docker info but I have no idea which problem they are even referring to as the error message from original report was gone already in v1.7.0. #22423 matches most of the descriptions in here and is fixed with v1.12. If you have trouble removing a container, please start a new issue, include information about the specifics of your container and daemon logs. If it is a hang then send SIGUSR1 signal to docker daemon and include it in the issue report as suggested in https://github.com/docker/docker/issues/10589#issuecomment-234693470 .

I'm closing this, blame him :point_up:

Guys, you are consolidating issues into one by telling they are the same issue which is OK. Then you are closing the issue complaining that there are multiple issues in one bug report.
People are looking for workarounds when they get no love in here. Closing issues without addressing the problem does not make any sense.

@gokhansengun If you have a problem in v1.12 then please start a new issue with full report data. Given that this was reported in v1.4 and you have something similar in v1.12 it is very unlikely that these problems have the same cause. As I said in my comment it is impossible that you got the same exact error message as it has been removed a year before v1.12 was released. At least some of the people here got a fix with #22423 or even earlier. If we have more issues left we need new report data about them so they can be solved.

Problem exists in:
Docker version 1.10.3, build 3cd164c
coreOS host

For what it is worth, my problem was related with the OS, namely Ubuntu 14.04. Changed it to Centos 7 and 50% repro on Ubuntu Box is now 0% on Centos 7. Both are running Docker version 1.12

@gokhansengun What is your 50% repro in ubuntu? If you have a reproducible testcase please open an issue for it so it can be fixed.

@tonistiigi a JMeter image based on official Java:7 image causes 99% cpu while running JMeter test scripts. I got rid of Ubuntu 14.04 alltogether but let me see what I can do. Will let the issue number given here.

I am unfortunately unable to reproduce it with using boxcutter/ubuntu1404 image with Vagrant. The original repro VM has already gone as said and I seem to have no way to reproduce now, sorry.

this is closed but i am running into a issue with the  same outcome as well as some other people on these tickets.
https://github.com/docker/swarm/issues/2304
https://github.com/docker/docker/issues/26017
all using swarm mode docker 1.2

I'm also having this issue with Docker for Mac @petetnt. Running Docker version 1.12.1 though.

I've seen this when running the dockcross/linux-arm64 container  (based on debian:jessie) under 1.13.0-rc3 on a Mac.  It is not reliable, but sometime interrupting a build with ^C will hang the process.  Attempting the restart docker will not work and the docker process is consuming 100% cpu.   The only way to fix it that I know of is to reboot the machine.
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.12.1
BuildVersion:   16B2555

$ docker version
Client:
 Version:      1.13.0-rc3
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   4d92237
 Built:        Tue Dec  6 01:15:44 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.13.0-rc3
 API version:  1.25 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   4d92237
 Built:        Tue Dec  6 01:15:44 2016
 OS/Arch:      linux/amd64
 Experimental: true

I have same or similar issue for docker 1.12.3 and 1.12.5. A process was killed. but docker still shows it in the list and docker stop container_id is stuck. Mostly images base on java. One of them official Elasticsearch images v2. Also have storage type overlay.

Having the same issue with Docker version 1.13.0, build 49bf474, ubuntu 14.04. After the container been running for a long period of time.

Hi,
I have encountered same problem. I had run mongodb, kafka images upon ubuntu 16.04
Please see belows,
docker stop broker02.1.1rf7j2a6njxycwjbc6hc069k2
Error response from daemon: Cannot stop container broker02.1.1rf7j2a6njxycwjbc6hc069k2: Cannot kill container e1da77e2e13b681312d8bd6bab019c607cc16b88a0696826b2593dc093d34047: rpc error: code = 14 desc = grpc: the connection is unavailable
docker version
Client:
Version:      1.13.0
API version:  1.25
Go version:   go1.7.3
Git commit:   49bf474
Built:        Tue Jan 17 09:58:26 2017
OS/Arch:      linux/amd64
Server:
Version:      1.13.0
API version:  1.25 (minimum version 1.12)
Go version:   go1.7.3
Git commit:   49bf474
Built:        Tue Jan 17 09:58:26 2017
OS/Arch:      linux/amd64
Experimental: false
Containers: 35
Running: 6
Paused: 0
Stopped: 29
Images: 13
Server Version: 1.13.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 151
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: active
NodeID: mvimcgosd3ajnul07i7s23puw
Is Manager: false
Node Address: <IP_ADDRESS>
Manager Addresses:
<IP_ADDRESS>:2377
<IP_ADDRESS>:2377
<IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: N/A (expected: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e)
runc version: 2f7393a47307a16f8cee44a37b262e8b81021e3e
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-62-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.797 GiB
Name: worker01
ID: 3BUL:LI3A:ZTCA:RKJE:VGDN:FNVG:5ROB:ZPFV:UYIN:W5AU:HMLK:VOA2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false

Hey,
Having the same running following
docker kill $(docker ps -qa)

Error response from daemon: Cannot kill container 0b9617dff904: Container 0b9617dff904520ccb903a861281c44a9a2ce7aa3bc3f024c779028fdb073b36 is not running

The docker version is

Client:
Version:      1.12.2-cs2-ws-beta
API version:  1.25
Go version:   go1.7.1
Git commit:   050b611
Built:        Tue Oct 11 02:35:40 2016
OS/Arch:      windows/amd64
Server:
Version:      1.12.2-cs2-ws-beta
API version:  1.25
Go version:   go1.7.1
Git commit:   050b611
Built:        Tue Oct 11 02:35:40 2016
OS/Arch:      windows/amd64

OS:

Caption                                   : Microsoft Windows Server 2016 Datacenter
OSType                                    : 18
Version                                   : 10.0.14393

@ValentinRueda looks not related to this issue; you specify -qa, which includes stopped containers; so the error message is correct, because a stopped container cannot be killed

I am locking the conversation on this issue, per https://github.com/docker/docker/issues/10589#issuecomment-246083333

I think we should close this. Like @thaJeztah said, this is a collection of unrelated problems. There are people commenting with their docker info but I have no idea which problem they are even referring to as the error message from original report was gone already in v1.7.0. #22423 matches most of the descriptions in here and is fixed with v1.12. If you have trouble removing a container, please start a new issue, include information about the specifics of your container and daemon logs. If it is a hang then send SIGUSR1 signal to docker daemon and include it in the issue report as suggested in https://github.com/docker/docker/issues/10589#issuecomment-234693470 .


Third edition of spaceship game

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

440 of 440 (100.0%)  changed or added relevant lines in 19 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.6%

Covered Lines:
1233

Relevant Lines:
1233

💛  - Coveralls


Fix NCProperties error

FAIL: test_no_global_attributes (main.TestNetCDFSave)
Traceback (most recent call last):
File "/home/h06/cbosley/Projects/iris/lib/iris/tests/test_netcdf.py", line 796, in test_no_global_attributes
'netcdf_save_no_global_attr.cdl'))
File "/home/h06/cbosley/Projects/iris/lib/iris/tests/init.py", line 361, in assertCDL
self._check_same(cdl, reference_path, type_comparison_name='CDL')
File "/home/h06/cbosley/Projects/iris/lib/iris/tests/init.py", line 493, in _check_same
type_comparison_name)
File "/home/h06/cbosley/Projects/iris/lib/iris/tests/init.py", line 239, in _assert_str_same
self.fail("%s do not match: %s\n%s" % (type_comparison_name, reference_filename, diff))
AssertionError: CDL do not match: /home/h06/cbosley/Projects/iris/lib/iris/tests/results/netcdf/netcdf_save_no_global_attr.cdl
--- Reference
+++ Test result
@@ -46,0 +47 @@

  :_NCProperties = "version=1|netcdflibversion=4.4.1|hdf5libversion=1.8.17" ;

What does it even mean???

This seems to be a problem that my PyCharm is having with getting all the bits of the scitools/default-next environment to talk to each other.  Not necessarily a problem in itself, certainly not for the big picture.  Might have to come back to it later though.

This is because of an ncdump version conflict, and can be got around by operating in a terminal in PyCharm in which a module load has been performed rather than just using the scitools Python interpreter.


DO NOT MERGE DIRECTLY: Factoring out of memoizing maps

This is just a sketch to show what I meant about factoring out the logic in those maps. If you think this tends towards clarity, you can use it for inspiration, if not, please throw it away.

Thanks for this.  I have used as inspiration and factored out some common code.
I have amended the approach slightly.  I've dropped the key -> internal key mapping from the common classes and am using a wrapping class instead.  I tried passing in a lambda to do the key -> internal key mapping but that got ugly because my mapping function is recursive :(

Glad to contribute! Yeah, Java 8 lambdas are a weird love/hate thing for me. Love that there is now something, hate the way it is. {grin} But then, I can't pretend that I would have done any better!


chore(release): prepare release 0.5.6

Description
Prepare the release for v0.5.6.
Checklist

Code is easy to understand
No obvious errors or bugs
CI/CD Pipelines did run successfully
Tests were implemented
Documentation was created

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!


[stable/spinnaker] Fix the wrong config path for minio image tag

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

No
What this PR does / why we need it:
As reported on https://github.com/helm/charts/issues/14250 , specifying a minio image tag with minio.imageTag has no effect and image minio/minio:RELEASE.2018-08-25T01-56-38Z has been used.
This PR specifies a minio image tag with minio.image.tag so that the chart users can use a minio image they want.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #14250

Special notes for your reviewer:
In order not to couple the config path fix with minio version change, I specified the tag RELEASE.2018-08-25T01-56-38Z that the current chart generates (i.e. 1.23.1), instead of specifying the tag RELEASE.2019-02-13T19-48-27Z that was given in values.yaml but actually not in use.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @dwardu89
Thanks for your time 😃

@dwardu89 knock knock :smiley:

/ok-to-test

/lgtm

Thanks @dwardu89 for reviewing the change :wink:


Hatch multiple eggs

Can you add a feature to use all the incubators you have and hatch multiple eggs at the same time?

It should be issues of PokemonGo-Bot. This desktop project is just a UI layer. You should check the bot repository.

https://github.com/PokemonGoF/PokemonGo-Bot-Desktop/issues/138

@tnsbm How is that related with hatching multiple eggs?


"Enter" Submits Settings Form

Pressing the "Enter" key now allows the user to submit the edit settings form.
Closes Issue #356

Hi @jlewenthal2004 , thanks for your work here!
Typically, work for different features is done in different Pull Requests. Would you be able to please create different pull requests for each of the different features you work on? I see there are many commits here in this one pull request for many different features. I'd like to be able to review and merge each separately. As it stands now, if I merge this one pull request I get all the changes, which is not ideal.

Also, I see you are still working inside of your fork, which is many commits behind main.

Lots of things have changed in the codebase since you forked, so changes made in your version may not work in the latest version. Do you think you could update your fork, or work directly from this repo? Thanks!

Closing as stale.


XHTML tags in documentions

In the Matroska EBML Schema we use some XHTML elements in documentation a, br and strong. They are understood by Markdown and the RFC generators. We should mention them in the spec.
It's already allowed in the XSD Schema after #273

closed via https://github.com/cellar-wg/ebml-specification/pull/275


Language Module Integration

A module known as "Obsidian" or https://bitbucket.org/Fyorl/obsidian/src/master/ could work wonders as using both Obsidian and Polyglot just doesn't work, this is because Obsidian is using a different character sheet then the default and well it would be nice if Polyglot could recognize Obsidian's sheet, so maybe a support?
Yeah, I couldn't figure out the pull request if this is where it goes.

Sorry, I won't support obsidian.
While I love what Fyorl did with obsidian and it looks gorgeous, the problem is that I think obsidian is modifying the system's data and using its own custom data format. That's a very dangerous thing to do because it means if you disable the module, then your actor becomes broken and you loose your content, and you can't use a different sheet with the actor anymore. Regardless, the actor data format is defined by the system, not but a module. I know that Fyorl was told he shouldn't do this and I don't know if he has plans to migrate his data to match the dnd5e system's template, but until he does, it won't work, and polyglot will certainly not be the only module that will be incompatible with obsidian and forcing everyone to add special cases for any module that doesn't do things correctly is not a viable long term, or scalable solution.
This is my assumption on information known to me for a while which may be outdated, so if I'm mistaken, feel free to correct me.

Sorry, I won't support obsidian.
While I love what Fyorl did with obsidian and it looks gorgeous, the problem is that I think obsidian is modifying the system's data and using its own custom data format. That's a very dangerous thing to do because it means if you disable the module, then your actor becomes broken and you loose your content, and you can't use a different sheet with the actor anymore. Regardless, the actor data format is defined by the system, not but a module. I know that Fyorl was told he shouldn't do this and I don't know if he has plans to migrate his data to match the dnd5e system's template, but until he does, it won't work, and polyglot will certainly not be the only module that will be incompatible with obsidian and forcing everyone to add special cases for any module that doesn't do things correctly is not a viable long term, or scalable solution.
This is my assumption on information known to me for a while which may be outdated, so if I'm mistaken, feel free to correct me.

Darn, well I hope he changes his mind then, thanks!


Bugfix/reset categories

What

Reset categories when changing the venue

How

Pass the currentVenueName prop to the Sidebar and Bottom sheet, and then to the Search component
Implement useEffect hook and listen to the changes in the currentVenueName
If there is a selected category, deselect it and clear the results list

Do these changes break anything in case no venue prop is provided to the map template?

No, because if there is no venue prop then we also don't have any categories to show, unless you select a venue from the venue selector.

No, because if there is no venue prop then we also don't have any categories to show, unless you select a venue from the venue selector.

I am not sure that is the intended behaviour, since a venue should always be chosen. But it's definitely not related to those changes anyway.


Workspace region not supported

I am following all the steps in this page but when I launch visual interface I get this message: "Your workspace in current region is not supported". I used Canada Central as it shows on this page. Could you please advise?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f5de7955-4cd6-efdb-f528-ef985b846e40
Version Independent ID: a54426e1-f620-2473-4bc3-b5bd2892cb21
Content: Quickstart: Prepare and visualize data without writing code - Azure Machine Learning service
Content Source: articles/machine-learning/service/ui-quickstart-run-experiment.md
Service: machine-learning
Sub-service: core
GitHub Login: @sdgilley
Microsoft Alias: sgilley

@cfauchere Hi Clement, I am very sorry about your experience. For now, Visual Interface is currently not available in the Canada Central Region. It will be available by the end of June.

@cfauchere We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Compile error after i18n

Error message
TypeError: (0 , _pages_en_md_nextra_raw__WEBPACK_IMPORTED_MODULE_3__.getStaticProps) is not a function
  11 |   const locale = context.locale;
  12 |   if (locale === 'en' && true) {
> 13 |     return page_data_0(context);
     |                       ^
  14 |   } else {
  15 |     return {
  16 |       props: {}

Reproduce procedure:
Follow the steps.
This only happens after I changed /pages/posts/pages.md to /pages/posts/pages.en.md, and only for this particular file. If I delete this md file, the error disappears.
Not sure what's causing it at the moment, but looks like in the loader.js at line 205, when trying to import getStaticProps from './${file.name}?nextra-raw' it returns undefined.

Hi @arange, do you still have this problem?


Add 'Scope and Usage' to all profiles

Describe the purpose and usage of each profile, to make the IG more readable.

Is handled


Add project folders framework

manager.py is also a very long file, and hard to review. I'd move as much code out into other modules as possible.

agree, have factored out configs and some utils. ATM utils of different type (ssh, directory managerment) are combined into a utils file but will be worth factoring out of separate files as it gros.

Lastly, the code line length is formatted, but it would be good to do the same with the docstrings. Some are very long.

thanks have done.
Am currently writing tests which will be useful to see how optimal pyftpsync is for our needs. It might be worth using rysnc / robocopy directly rather than pyftpsync which uses sftp commands directly, but doesn't provide as much extra checking (e.g. checksum options).

Am currently writing tests which will be useful to see how optimal pyftpsync is for our needs. It might be worth using rysnc / robocopy directly rather than pyftpsync which uses sftp commands directly, but doesn't provide as much extra checking (e.g. checksum options).

Sounds good. I guess there's a package out there for doing these checks?


⚠ Bofrost.be has degraded performance

In 8e88717, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1575 ms

Resolved: Bofrost.be performance has improved in 1bf7d0a after 1 hour, 2 minutes.


take_until_and_consume should be renamed to take_until_and_skip

I think that take_until_and_consume! is confusingly named.
The documentation for take_until_and_consume says:

take_until_and_consume!(tag) => &[T] -> IResult<&[T], &[T]> generates a parser consuming bytes until the specified byte sequence is found, and consumes it

However, the README describes this macro as:

take_until_and_consume!: will take as many bytes as possible until it encounters the provided byte array, and will skip it

To me, the use of "consuming" and "consumes" in the macro documentation implies to me that the tag sequence will be included in the result; however, the tag sequence is discarded.
I think that the current take_until_and_consume should be renamed to take_until_and_skip, and the behavior of take_until_and_consume should be changed to include the tag sequence in the result.

At the very least, I think that it should explain that the tag is not included in the output in the docs.


Correct trigger definition

It looks to me that the 'employees_delete' trigger definition should have BEFORE DELETE instead of BEFORE INSERT.

Thank you.


add White gateway

Adding a basic description on there:
White is a payment solution for developing countries .. countries that have long been neglected by larger payment solutions. It's like Stripe, and is starting off in the Middle East before expanding to other developing regions soon.

+1

@ntalbott hi Nathaniel -- is active_merchant still alive?

@yazinsai for sure, but the maintainers have day jobs, and adding new gateways is non-trivial. We do eventually get to everything, but sometimes it takes months before we get a chance to clear out the backlog.

@ntalbott I can imagine -- is there anything we can do to help take some of that load off you guys, and thereby get requests approved quicker?

Hey folks, looks like White has been superseded by Payfort? Can I close this out?

yes. it can be closed. we (as Payfort) have a new solution, probably we will have to submit new PR :)

@alovak hopefully I can get to it faster this time!


set joint position of robot

Hi,
I need to set robot's joint position to make data, but when I use env.step(action) it is too slow to get there, I need 40 iterations to get there
Thanks

Dear @kimchicanh ,
you can set the positions (and velocities) of the robot joints instantaneously by using the reset_current_position(pos, vel) method.
Example:
import numpy as np
import real_robots
import gym

env = gym.make('REALRobot-v0')
env.render('human')
env.reset()

pos = np.pi / 4
vel = 0
robot = env.robot

for i in range(7):
    robot.jdict["lbr_iiwa_joint_%d" % (i+1)].reset_current_position(pos, vel)

robot.jdict["base_to_finger00_joint"].reset_current_position(0, 0)
robot.jdict["base_to_finger10_joint"].reset_current_position(0, 0)
robot.jdict["finger00_to_finger01_joint"].reset_current_position(0, 0)
robot.jdict["finger10_to_finger11_joint"].reset_current_position(0, 0)

This is useful to create some data for debugging/training/testing algorithms during development; however, when making submissions for the competition, it is assumed that the controller does not have access to these function, and it should gather data for its learning by interacting normally with the environment (i.e. not resetting itself instantaneously).

@emilio-cartoni thanks you so much

Notice that using this function, joints can be set to values that are normally impossible to reach:
i.e. it is possible to set the joints beyond their (-pi/2, +pi/2) limits or to put the robot arm inside the table.

@emilio-cartoni Thanks for your information, I have a problem with target porsition of camera, How to change it?, I set self.set_eye("eye", eye_pos=[0.01, 0, 1.4], target_pos=[100,0,0]) but nothing happen
Thanks

Dear @kimchicanh ,
you can change the eye position as in the following:
import numpy as np
import real_robots
import gym
import matplotlib.pyplot as plt

env = gym.make('REALRobot-v0')
env.render('human')
env.reset()

plt.figure()
plt.imshow(env.step(np.zeros(9))[0]['retina'])
plt.title("Standard eye")

env.set_eye("eye", eye_pos=[0.01, 0, 1.4], target_pos=[100,0,0])
env.reset()  # This is necessary after using set_eye
plt.figure()
plt.imshow(env.step(np.zeros(9))[0]['retina'])
plt.title("Modified eye")

The target_pos parameter has no influence for the retina observation, since when the retina image is computed, the target is always the table.
See get_retina in REALRobotEnv
    def get_retina(self):
        '''
        :return: the current rgb_array for the eye
        '''
        return self.eyes["eye"].render(
                                       self.robot.object_bodies["table"]
                                       .get_position())

which calls render in EyeCamera
    def render(self, *args, **kargs):
        if self.pitch_roll is True:
            return self.renderPitchRoll(*args, **kargs)
        else:
            return self.renderTarget(*args, **kargs)

and then calls renderTarget in EyeCamera:
    def renderTarget(self, targetPosition, bullet_client=None):

        if bullet_client is None:
            bullet_client = self._p

        self.targetPosition = targetPosition

        view_matrix = bullet_client.computeViewMatrix(
                cameraEyePosition=self.eyePosition,
                cameraTargetPosition=self.targetPosition,
                cameraUpVector=self.upVector)

        proj_matrix = bullet_client.computeProjectionMatrixFOV(
                fov=self.fov,
                aspect=float(self.render_width)/self.render_height,
                nearVal=0.1, farVal=100.0)

        (_, _, px, _, _) = bullet_client.getCameraImage(
                width=self.render_width, height=self.render_height,
                viewMatrix=view_matrix,
                projectionMatrix=proj_matrix,
                renderer=pybullet.ER_BULLET_HARDWARE_OPENGL
                )

        rgb_array = np.array(px).reshape(self.render_height,
                                         self.render_width, 4)
        rgb_array = rgb_array[:, :, :3]

        return rgb_array

Beware that changing the eye position is not allowed for submissions :)


chore(main): release ngx-intl 2.1.2

:robot: I have created a release beep boop
2.1.2 (2023-05-26)
Bug Fixes

test ci automation (8c0d47c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/haiilo/ngx-intl/releases/tag/ngx-intl-v2.1.2 :sunflower:


Cannot set displayNum: 0

Title says it all. Constructor option displayNum is not taken into account if value is set to 0.

Try passing the value as a string instead of a number, i.e. displayNum: "0" instead of displayNum: 0

Shockingly, that worked. Thanks for that.
So "0"==true evaluates to false but  "0" ? true:false evaluates to true.

In case you're interested:
"0" is a non-empty string, so it is truthy - https://developer.mozilla.org/en-US/docs/Glossary/Truthy
0 is falsey by definition - https://developer.mozilla.org/en-US/docs/Glossary/Falsy

Published 0.4.0 with your PR.


Missing link?

Learn more about determining [relative latencies between Azure regions and internet service providers](#determine-relative-latencies-between-azure- regions-and-internet-service-providers) and how to monitor communication between a VM and an endpoint with connection monitor. - There are some issues with this sentence, looks like proper link is missing.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 792330d5-29ee-3fe9-bc22-cad868ca45ed
Version Independent ID: 614de29c-ba8b-0c26-32cc-928f289cd50c
Content: Azure Network Watcher
Content Source: articles/network-watcher/network-watcher-monitoring-overview.md
Service: network-watcher
GitHub Login: @jimdial
Microsoft Alias: jdial

@lzieba91 Thanks for the Feedback! I will get this link corrected.

@lzieba91 I have fixed the link, the document should update within 24 hours.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add basic forking coverage support

@louismerlin  can be merge this?

No, there is some feature-related stuff I don't like, let me take a look, maybe I can fix it quickly

Cool, the feature-related stuff was just artifacts of previous versions of this code. I'll merge this as soon as the CI is green, and publish v0.8.1.


Easier markings

Fixes #56.

Codecov Report

Merging #60 into master will increase coverage by 0.02%.
The diff coverage is 100%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e215165...2bdf834. Read the comment docs.


[WIP] Render API docs

Render API schema as part of documentation.

A snapshot of each schema will be available at each release, and also for "latest" (master)
API schema file available for download (.yaml file)

References

https://github.com/inventree/InvenTree/pull/6319
https://github.com/inventree/InvenTree/issues/6350
https://github.com/inventree/InvenTree/issues/6269

Seems reasonable. Is the api supposed to be rendered already?

It did not seem to be rendering reliably with that library. I have tried a new one - check it out now and see what you think

The generated schema file (.html) is 16MB - which might take some time to load. Do we think this is an issue?

This is really laggy to open with a browser. How about splitting it in multiple pages categorized by the Django apps, so each apps api has a sub page. This reduces the download size and also the page size.

@wolflu05 nice idea - any idea how to achieve that?

Not really sure about how to support that, the mkdocs plugin seems like it's not. So we would need to either find a way to export the schema for each app individually or write a script to divide the schema into multiple pieces and then generate multiple pages that use the OAD plugin.

or write a script to divide the schema into multiple pieces and then generate multiple pages that use the OAD plugin.

Looking into this approach, doesn't seem too bad...

Ok @matmair @wolflu05 I have a pipeline working - please check out the rendered docs and LMK what you think of the current state

This already looks pretty good. Awesome work.
But I would adjust a few things:

at the bottom of each page are all models listed, maybe only list the required models for each sub page when splitting the schema
maybe improve the navigation between the sub pages, so that I don't need to first click on the Extend > InvenTree API > API schema and then select to correct sub page (eg plugin) on the api schema page, but instead maybe Extend > InvenTree API Schema > Plugin or Extend > InvenTree API Schema > Overview for the index page
is it correct that if a new Django app is added, a new api markdown file needs to be created and the schema splitting tool needs some adjustments to the list of sub pages?

@wolflu05 can you suggest how to implement any of those? Otherwise I'd be keen to merge this as is, and work on improvements in a later PR.. Thoughts?

while splitting the schema, analyze all referenced models and only output those in the splitted schema. This drastically will improve page performance and load speed
Already explained how we could do that, by moving the api schema documentation one level more to the top of the navigation like we did with plugins and plugin mixins.
We could maybe auto discover the available apps, but I think the current solution with adding it manual is sufficient. (I guess the machine API needs to be added since #4824 is merged?)
That can't be easily solved here, we would need to improve the used plugin, but I think that's just a nice to have, so keeping it like now is fine

@wolflu05 point 1) should be implemented now, 3) and 4) I think would be not possible without digging into the plugin some more. LMK what you think as now

Performance and load speed is much better now, thank you really much. Maybe it's worth putting the machine api endpoints into its own page, but I'm happy with it now.

@wolflu05 seems like the machine API is throwing an error and not building https://github.com/inventree/InvenTree/actions/runs/7959068634/job/21725283385?pr=6463#step:4:40

@wolflu05 seems like the machine API is throwing an error and not building https://github.com/inventree/InvenTree/actions/runs/7959068634/job/21725283385?pr=6463#step:4:40

@matmair why is the CI passing then - the API schema errors should cause CI to fail...

@wolflu05 I have split machines out into their own path now

Thank you.
This error is interesting, because there is actually a correct schema annotation with extend_schema. Maybe this error caused no ci fail, because only the OAD plugin which generates the md fails and not while exporting the schema?

@SchrodingersGat as far as I can read the CI runs the API schema task failed and threw an error

Yes, but not the generation step. That passed. The difference checking step is the step that failed. Has that something todo with the ongoing gh actions beta where there are bugs from time to time like this?

It fails within the CI job, I think that is enough

I see, but why does the ci does not fail on master then? The machine api is already merged in there.

@matmair @wolflu05 any ideas how we should proceed here? This is the final blocker for the 0.14.0 release

AFAIK there is a schema issue and a problem with translations; I have just restarted the docs CI - maybe it runs now

@matmair any chance you can have a look at this? I am still a bit confused by the CI process here

@SchrodingersGat The issue occurs while exporting the schema. A requests serializer is missing for introspection in one of the machine API serializers. However this doesn't throw an error, but instead the schema.yml file is not created, so a later step expecting this file failed because it cannot find it.
Regarding the machine api error it seems like this can be fixed with this patch:
diff --git a/InvenTree/machine/api.py b/InvenTree/machine/api.py
index 9448d2ea9..2fec1b4cc 100644
--- a/InvenTree/machine/api.py
+++ b/InvenTree/machine/api.py
@@ -144,7 +144,7 @@ class MachineRestart(APIView):

     permission_classes = [permissions.IsAuthenticated]

-    @extend_schema(responses={200: MachineSerializers.MachineRestartSerializer()})
+    @extend_schema(request=None, responses={200: MachineSerializers.MachineRestartSerializer()})
     def post(self, request, pk):
         """Restart machine by pk."""
         machine = get_machine(pk)

And to already fail in the export step, we may could check for the existence of the file and if not exit 1.


[FEATURE] make builder class and methods also private if constructor is private

Describe the feature
When having this:
public class User {

@Builder
private User(String name, Task task){

}

}
or this
public class User {

@Builder
private static User build(String name, Task task){

}
}

then lombok generates public generated builder classes (methods) instead of private.
Lombok should look at the constructor or static method defined visbility (for example, private or public) and use this for its builders.

Disclaimer: I'm not a Lombok team member, so just an opinion here.
Sometimes you want the builder to be the only way of instantiating your class, together with customizing the fields of the builder. In this case, you would do exactly that: define a private constructor and put @Builder on it.
So there is a use case for the current behavior, too.
It's difficult to decide which use case is the more common one.
However, changing Lombok's behavior here would be a breaking change. Furthermore you can use @Builder(access = AccessLevel.PACKAGE) to set the access level. So although your request sounds reasonable, I think it's better to stick with the current behavior.

Agree with Jan. There is a valid use-case for the current behaviour, and a way to change it, so there is no sense in breaking backwards compatibility


scanner scans all characters as c6

Current Behavior
scans the locked constellations as unlocked
Expected Behavior
The scanner stops scanning
Reproducing a Behavior
scan characters ig?
Device OS
Windows 11
Genshin Impact Version
2.8
Inventory Kamera Version
1.2.8
Screen resolution, screen mode, and UI scale
1280x720
Additional notes and remarks
No response
Evidence
No response
Preflight Checklist

[X] I have checked for similar issues in the issue page, and I have not found any similar to mine.
[ ] I am using the latest version of the scanner.
[ ] I tried setting the scanning delay to maximum, and it still doesn't work.
[ ] I have attached the video recording to the bug report.
[ ] I have attached the error log to the bug report.
[ ] I am available to later explains the issue.
[X] I have disabled all screen filtering software or plugins (i.e. HDR, Image Sharpening) while scanning.
[X] I use default in-game keybindings or have configured keybindings for the scanner.

I am closing this issue as it is a duplicate


Add NewDiagram to allow creating new diagrams from plain diagram.Options

This PR makes it possible to create a diagram from a plain *diagram.Options struct.
The motivation behind this PR is that one cannot set the Name field of a diagram's options.
While the preferred way of creating a diagram seems to be passing Option functions that override the default ones, allowing the user to simply pass the object is much more flexible.
It is also not possible to create a Name function that would set that field, because the diagram package already contains such a function that sets a node's name.
Maybe all node-related functions should be moved to a separate package to avoid such collisions?

Indeed, separate package is the right approach. I have some changes I'll commit in the next few days and we can revisit.

@tntobias Great! Please ping me when we can have another look at this.

I've pushed a refactor to the api to branch 'next'. As you can see, much has changed. This doesn't change much with regard to construction via pure Options struct as you've proposed but I can see creating configuration structs that can be passed to a constructor that results in a specific attribute set. I haven't demonstrated that yet but will do so as soon as I've corrected the examples and added some tests.


explorer overwrites its contents while scrolling a long file list

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.90.0
OS Version: Linux x64 6.6.15-amd64

Steps to Reproduce: Have a long file list in the explorer

It would be better to have a cleaner explorer!

How big of a file list is this? I've tried on the VS Code repository and cannot reproduce.

You wrote you couldn't see it, I was thinking about if something with my settings could make it. Try setting "sideBar.background": "#00000002".

Looks like sticky scroll + missing background in explorer/side bar.
Adding non-opaque sideBarStickyScroll.background should help

"sideBar.background": "#f0f0f0" will be good!


Null check operator used on a null value

Plugin Version
google_mobile_ads: ^0.13.2
Flutter 2.3.0-17.0
Dart 2.14.0
Steps to Reproduce

paste google mobile ads in pubspec.yaml and run 'flutter pub get'.
paste this line in flutter's main function.
MobileAds.instance.initialize();
After run, will see below error.
Null check operator used on a null value

Expected results:
App should be run.
Actual results:
Error: Null check operator used on a null value

Logs
[VERBOSE-2:ui_dart_state.cc(213)] Unhandled Exception: Null check operator used on a null value            #0      MethodChannel.binaryMessenger (package:flutter/src/services/platform_channel.dart:121:86)            #1      MethodChannel.setMethodCallHandler (package:flutter/src/services/platform_channel.dart:375:5)            #2      new AdInstanceManager (package:google_mobile_ads/src/ad_instance_manager.dart:44:13)            #3      instanceManager (package:google_mobile_ads/src/ad_instance_manager.dart:32:37)            #4      instanceManager (package:google_mobile_ads/src/ad_instance_manager.dart)            #5      MobileAds._init (package:google_mobile_ads/src/mobile_ads.dart:77:5)            #6      MobileAds._instance (package:google_mobile_ads/src/mobile_ads.dart:36:53)            #7      MobileAds._instance (package:google_mobile_ads/src/mobile_ads.dart)            #8      MobileAds.instance (package:google_mobile_ads/src/mobile_ads.dart:39:36)            #9      main (package:helloads/main.dart:7:13)            #10     _runMainZoned.<anonymous closure>.<anonymous closure> (dart:ui/hooks.dart:142:25)            #11  <…>

Documentation make me assume it requires only 'MobileAds.instance.initialize()'.
I did not include the 'ensureInitialized()' function. Adding that function solved my error.
Thanks
WidgetsFlutterBinding.ensureInitialized();
MobileAds.instance.initialize();


Unused features removed.

PAPI profiling tool: please use the Intel VTune profiler
The symmetric mode load-balancing: please KNL stand-alone clusters instead of KNC

Jenkins: Automatic build-test is triggered.

Jenkins: Automatic build-test is started.

Jenkins: Automatic build-test is successfully finished.

Thank you @yhirokawa san, I will check this PR later...


Add common security group rule values

Many security groups need common rules for egress or ingress applying - for example the following to allow all traffic (commonly used for egress to match the AWS console):
{
    protocol: "-1",
    fromPort: 0,
    toPort: 0,
    cidrBlocks: ["<IP_ADDRESS>/0"],
    description: "Allow All Traffic",
}

Since these require memorising the combination of port and protocol (e.g. is it from 0 to 2^16-1, vs from 0 to 0 when used with protocol -1), we should add convenience structures to the overlays with some common rules defined.
I'd suggest (for now):

All traffic from anywhere
Function for all traffic from a given CIDR block array
Function for a single TCP/UDP port from anywhere
Function for a single TCP/UDP port for a given CIDR block array

@jen20 do we want to add this to the provider or into awsx? or both?

It's not clear how we could use awsx security group with multiple protocols (TCP and UDP)


Store prev and next page url in document

Just something I realized while looking at the JS - there's no need to trigger an extra request to the backend API.

That was some nice non-sense there :-) Nice catch.


/media/pk_from_url not working

Python console
>>> Client().media_pk_from_url("https://www.instagram.com/p/CTZRfJEDsE7/")
2655230362137837883

API request:

API logs:
api_1  | https://www.instagram.com/p/CTZRfJEDsE7/
api_1  | INFO:     <IP_ADDRESS>:39612 - "GET /media/pk_from_url?url=https%3A%2F%2Fwww.instagram.com%2Fp%2FCTZRfJEDsE7%2F HTTP/1.1" 200 OK

I added in a print to see the URL is correct... not sure why it's not working, and appears to be adding extra zeroes

Why do you think it doesn't work? Your screenshot has the correct answer:

I don't get it?

I don't get it?

Describe your question in more detail

Service
response

Python gives
2655230362137837883

API gives
2655230362137838000

API is giving wrong data...?

@Soneji now I see the problem, thanks!


add reviews

working bottom up and having ~70 articles to do.
this will work out, even if more than one person is at the same page, won' t it ?

saved everything from the 148 texts...


{Synapse} Fix #29576: az synapse workspace parameter help message cause doc auto autogenerated build error.

Related command

az synapse workspace create&update
Description

Remove parameter help message "https://github.mydomain.com" to fix issue.
https://github.com/Azure/azure-cli/issues/29576
Testing Guide

History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Synapse


Allow multiple .sjcsrc files

I have a .jscsrc file at the root of my project, which is cool, but it would be nice to be able to drop additional .jscsrc files into sub-directories to allow different rules to be enabled/disabled on a per-directory basis

Yeah, we have a long standting ticket about that - https://github.com/jscs-dev/node-jscs/issues/1106, if you would help us with it, it would be great!

Sorry for the dupe! I'll take a look at the other ticket :)


Error: (4, 'cannot read key')

Hi,
When I do
key = xmlsec.Key.from_file('~/signing_key.pem',xmlsec.constants.KeyDataFormatPem)
Getting Error: (4, 'cannot read key')
Unable to find why is it failing to read the private key file.

Hi. Seems like your private key is not valid or is not in PEM format. You can check validity of key file by using OpenSSL.

it should be something like:
-----BEGIN RSA PRIVATE KEY-----
body of key
-----END RSA PRIVATE KEY-----
you can also check the private key via openssl
openssl rsa -in jam-private.pem -check

I did check the validity and got the below response
$openssl rsa -in signing_key.pem -check
RSA key ok
writing RSA key
-----BEGIN RSA PRIVATE KEY-----
<KEY BODY>
-----END RSA PRIVATE KEY-----

But when I do
key = xmlsec.Key.from_file('~/signing_key.pem',xmlsec.constants.KeyDataFormatPem)
getting
Error: (4, 'cannot read key')

Ah. I am sorry.
the problem in your path. xmlsec does not have code to expand user home directory. '~',
xmlsec expects abs or relative path, which expanded variables.
you can use os.path.expanduser to get abs path for the instance.
try this:
key = xmlsec.Key.from_file(os.path.expanduser('~/signing_key.pem'),xmlsec.constants.KeyDataFormatPem)

Thanks that helped.

Can i read key from a variable ?


don't mute connection when listener is absent

Corrected tests for #7 to account for expected new behavior.
Fixes #6

@alexcesaro @zstyblik Hopefully a version with passing tests is more palatable. Or at least can spark a conversation.
I also would like to remove launch order dependencies. Having the stats emitted and available when the collector finally comes up is the behavior I would expect.

@christian-blades-cb, cool :)

Any estimation when to expect the PR to be merged?
This functionality is desired.
Thank you.

@vchernoy Given that @alexcesaro hasn't pushed any commits since April, it's probably time to either fork this repo or move on to a different one. I chose cactus/go-statsd-client for my recent production work.


Adding --minfy causes unexpected "/js/jquery.tagcloud.js" in binding

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.84.1-4BD65E22 linux/amd64 BuildDate=2021-06-24T11:44:23Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?
I think this is the latest release. It did not do this on 0.79.
The code from my partials/footer.html.
<!-- jquery.tagcloud.js -->
<script>
    // only load tagcloud.js in tag.html
    if($('#tag_cloud').length !== 0){
        async("/js/jquery.tagcloud.js",function(){
            $.fn.tagcloud.defaults = {
                //size: {start: 1, end: 1, unit: 'em'},
                color: {start: '#bbbbee', end: '#0085a1'},
            };
            $('#tag_cloud a').tagcloud();
        })
    }
</script>

The cmd and err.
shadycuz-> hugo --gc --minify
Start building sites …
hugo v0.84.1-4BD65E22 linux/amd64 BuildDate=2021-06-24T11:44:23Z VendorInfo=gohugoio
Page.URL is deprecated and will be removed in a future release. Use .Permalink or .RelPermalink. If what you want is the front matter URL value, use .Params.url
ERROR 2021/06/26 07:06:29 unexpected "/js/jquery.tagcloud.js" in binding on line 606 and column 23
    4:         async("/js/jquery.tagcloud.js",function(){
                     ^
ERROR 2021/06/26 07:06:29 unexpected "/js/jquery.tagcloud.js" in binding on line 736 and column 23
    4:         async("/js/jquery.tagcloud.js",function(){
                     ^
ERROR 2021/06/26 07:06:29 unexpected "/js/jquery.tagcloud.js" in binding on line 842 and column 23
    4:         async("/js/jquery.tagcloud.js",function(){
                     ^
ERROR 2021/06/26 07:06:29 unexpected "/js/jquery.tagcloud.js" in binding on line 691 and column 23
    4:         async("/js/jquery.tagcloud.js",function(){
                     ^
Total in 193 ms
Error: Error building site: failed to render pages: unexpected "/js/jquery.tagcloud.js" in binding on line 899 and column 23
    4:         async("/js/jquery.tagcloud.js",function(){

This is upstream issue from tdewolff/minify.
minify failed if found js function named async.
Related issue in upstream JS: unable to parse if a function is named "async".
Already fixed in tdewolff/minify v2.9.17
Hugo still use tdewolff/minify v2.9.16

To be clear, your JS is technically okay, but they made async a keyword in later versions of JS, so naming a function async is an invitation for bugs that creep in when programs don't consider that async could be used as a normal variable name. I suggest the following edit to your footer to prevent future bugs:
<script>
    // only load tagcloud.js in tag.html
    if($('#tag_cloud').length !== 0){
        window.async("/js/jquery.tagcloud.js",function(){
            $.fn.tagcloud.defaults = {
                //size: {start: 1, end: 1, unit: 'em'},
                color: {start: '#bbbbee', end: '#0085a1'},
            };
            $('#tag_cloud a').tagcloud();
        })
    }
</script>

window.whatever is technically the same as whatever, but window.async is less likely to hit unexpected bugs like this.

Hi!
I just want to let you know that the minification of conditional chaining is still broken.


Hosted Pages V3?

From the documentation I can make out this won't work with hosted pages V3 no?
Thanks!

same

@aguilaair any update? I have same issue


[10.x] Add searchStrict method to Collection class

This pull request adds a new method searchStrict to the collection class that allows users to search for a value in the collection using strict comparison. The method simply calls the existing search method with the second argument set to true.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Revert Victory Charts removal

Decided that we will go ahead with the removal of Victory charts for this release


OverflowError: cannot fit 'int' into an index-sized integer

When I run the demo/run.py,i got an error.
encoded_inputs["attention_mask"] = encoded_inputs["attention_mask"] + [0] * difference
OverflowError: cannot fit 'int' into an index-sized integer

I cannot recall which line of code trigger this error. Please provide the full trace. Thanks.

These two photos contain all the error messages.

我不记得是哪行代码触发了这个错误。请提供完整的跟踪记录。谢谢。

these photos contain all the error messages.

It shows the error was raised from transformers package. Please check the package version.

It shows the error was raised from transformers package. Please check the package version.

i installed transformers==4.27.4,which is the right version.

I did a quick search and find that same issue happens to stable diffusion but did not find useful solution.
May I know what command you are using? And full list of your environment? Please provide as much detail as possible.

I did a quick search and find that same issue happens to stable diffusion but did not find useful solution.
May I know what command you are using? And full list of your environment? Please provide as much detail as possible.

it's the full list of my environment

And the full command to run with the full output.

以及要运行完整输出的完整命令。

it's the full command to run with the full output.

i wonder if you have encountered this error as well.can i solve this error by reinstalling the conda environment?

No, actually, this error does not seem to be related to our implementation. I didn't find any significant error in the above information. You may also check the downloaded pre-trained models.

you mean that maybe the error was caused by the pre-trained models?

No, actually, this error does not seem to be related to our implementation. I didn't find any significant error in the above information. You may also check the downloaded pre-trained models.

you mean that maybe the error was caused by the pre-trained models?

Just copy the title to google. You should be able to find the followings:
https://github.com/ostris/ai-toolkit/issues/70
https://github.com/CompVis/stable-diffusion/issues/860
I do not understand the solution proposed by them, but it seems not to be related with our repo.

Just copy the title to google. You should be able to find the followings: ostris/ai-toolkit#70 CompVis/stable-diffusion#860
I do not understand the solution proposed by them, but it seems not to be related with our repo.

I'v seen this,but it doesn't solve the error.

Can you try the model from #84?

Let me explain.
The tokenizer should have model_max_length from its config, which comes from the stable-diffusion models. However, if there is no model_max_length neither max_len in the config, the default value would be
VERY_LARGE_INTEGER = int(1e30)  # This is used to set the max input length for a model with infinite size input

which is from the transformers package. Therefore, if the wrong is loaded (especially the tokenizer), it may lead to your problem.
The solution is to load the correct model.

Let me explain.
The tokenizer should have from its config, which comes from the stable-diffusion models. However, if there is no neither in the config, the default value would bemodel_max_length``model_max_length``max_len
VERY_LARGE_INTEGER = int(1e30)  # This is used to set the max input length for a model with infinite size input

which is from the package. Therefore, if the wrong model is loaded (especially the tokenizer), it may lead to your problem.transformers
The solution is to load the correct model.

thanks,i wil try it .but i wonder which model do you use,where can i choose the model?

See my last comment.

May I know is your problem resolved?

May I know is your problem resolved?

I apologize for being delayed in replying to you due to some personal matters.Thank you very much for your guidance,and my problem has been resolved.