Dockly via Docker, container left behind
Jamesking56 opened this issue ยท comments
Expected Behavior
When running dockly via Docker and pressing q
to quit, the dockly container should no longer exist.
Actual Behavior
The container is left behind.
Steps to Re-produce the Problem
-
Launch dockly via Docker
-
Press
q
to quit -
Do
docker container ls -a
and see dockly still exists as a container
Context
- Operating System: Ubuntu 16.04.5 LTS
- Node.js version (run
node --version
): v8.15.0 - Package version: Latest, as its pulled via Docker
- Docker version (run
docker --version
): 18.09.0, build 4d60db4 - Is docker installed locally? Yes
- Do you have containers created? Yes
- Does this file exists
/var/run/docker.sock
? Yes - Output of
docker info
:
Containers: 3
Running: 3
Paused: 0
Stopped: 0
Images: 15
Server Version: 18.09.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-141-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.63GiB
Name: wp-096-du
ID: UCMJ:G67O:OES4:Y72N:C34V:NDNC:JAX6:WQKE:CUZE:XL6F:NXOA:S7ID
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: jamesking56
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
WARNING: No swap limit support
๐ This issue has been resolved in version 3.9.0 ๐
The release is available on:
Your semantic-release bot ๐ฆ๐