Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dockly via docker, hide itself

See original GitHub issue

Expected Behavior

If I run Dockly via Docker, it should not show itself in the running containers list.

Actual Behavior

It appears in the running containers list.

Steps to Re-produce the Problem

Launch Dockly via Docker
Check the list to see if it includes Dockly.

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

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

Xantioscommented, Feb 4, 2019

I dont see how that is a bug or a issue at all? If you list containers using docker ps it should list all containers and i don’t see why dockly should have other behaviour ?

2reactions

Jamesking56commented, Jan 2, 2019

Nope, just so that its hidden to stop any accidental stuff.

Pairs slightly with #86 - as if the container you’re running removes itself anyway then there is no reason for dockly to show it in the list.

Top Results From Across the Web

Manage sensitive data with Docker secrets

Secrets are encrypted during transit and at rest in a Docker swarm. A given secret is only ... You cannot remove a secret...

docker system prune - Docker Documentation

docker system prune: Remove all unused containers, networks, images (both dangling and unreferenced), and optionally, volumes.

Docker security

the attack surface of the Docker daemon itself;; loopholes in the container configuration profile, either by default, or when customized by users. the...

docker rm - Docker Documentation

Use the docker container prune command to remove all stopped containers, or refer to the docker system prune command to remove unused containers...

Isolate containers with a user namespace

Docker does not use them while userns-remap is enabled. Disable namespace remapping for a container . If you enable user namespaces on...