You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some fin commands result in a randomly-named container being left behind (based on the docksal/empty image). After using Docksal for a number of projects, you can accumulate a lot of these docksal/empty containers, and they have to be manually pruned with docker rm.
Steps to reproduce the issue:
Assuming you have a Docksal project already, and you are in the Docksal project root directory...
Run docker ps -a to get a list of all containers. Keep the output handy somewhere, to use for comparison later.
Run fin addon install adminer. Wait until finished.
Run docker ps -a again. Note that the adminer container has been added, AND a randomly named container has also been created, from the docksal/empty image.
Describe the results you received:
After installing the adminer addon, we see that the adminer container has been created, and another randomly-named container was created a few seconds earlier. Specimen output from docker ps -a follows:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6d3514a0ef68 adminer "entrypoint.sh docke…" 50 seconds ago Up 49 seconds 8080/tcp d8media_adminer_1
6e63fa4b8b99 docksal/empty "/bin/sh" 52 seconds ago Exited (0) 51 seconds ago elegant_bartik
0157e4384d8d docksal/apache:2.4-2.3 "httpd-foreground" 5 minutes ago Up 5 minutes (healthy) 80/tcp, 443/tcp d8media_web_1
73fa6af8258a docksal/cli:2.6-php7.2 "/opt/startup.sh sup…" 6 minutes ago Up 49 seconds (healthy) 22/tcp, 3000/tcp, 9000/tcp d8media_cli_1
8b11eda0578c docksal/mysql:5.6-1.4 "docker-entrypoint.s…" 6 minutes ago Up 6 minutes (healthy) 0.0.0.0:32768->3306/tcp d8media_db_1
b65701ced8cc docksal/ssh-agent:1.2 "docker-entrypoint.s…" 8 days ago Up About an hour (healthy) docksal-ssh-agent
381fda0ef946 docksal/dns:1.1 "docker-entrypoint.s…" 8 days ago Up About an hour (healthy) 192.168.64.100:53->53/udp docksal-dns
e286cbc3168f docksal/vhost-proxy:1.5 "docker-entrypoint.s…" 8 days ago Up About an hour (healthy) 192.168.64.100:80->80/tcp, 192.168.64.100:443->443/tcp docksal-vhost-proxy
...
... more containers, not relevant
Describe the results you expected:
I wasn't expecting to see the extra docksal/empty container.
Is this a single-use container, that could be removed by fin after it has done it's job?
The only mention of this image in the fin script is in a function called is_docker_path(). Tracing this back through check_docker_path(), it looks like these containers are being created anytime up() is run.
Description
Some
fin
commands result in a randomly-named container being left behind (based on thedocksal/empty
image). After using Docksal for a number of projects, you can accumulate a lot of thesedocksal/empty
containers, and they have to be manually pruned withdocker rm
.Steps to reproduce the issue:
docker ps -a
to get a list of all containers. Keep the output handy somewhere, to use for comparison later.fin addon install adminer
. Wait until finished.docker ps -a
again. Note that the adminer container has been added, AND a randomly named container has also been created, from thedocksal/empty
image.Describe the results you received:
After installing the adminer addon, we see that the adminer container has been created, and another randomly-named container was created a few seconds earlier. Specimen output from
docker ps -a
follows:Describe the results you expected:
I wasn't expecting to see the extra
docksal/empty
container.Is this a single-use container, that could be removed by
fin
after it has done it's job?The only mention of this image in the
fin
script is in a function calledis_docker_path()
. Tracing this back throughcheck_docker_path()
, it looks like these containers are being created anytimeup()
is run.Output of
fin config
:fin config output
Output of
fin sysinfo
:fin sysinfo output
(Note: I censored one of my project names in the output below.)The text was updated successfully, but these errors were encountered: