Both the accessy syncer and the email dispatcher docker container creates unnamed docker volumes. This itself makes it hard to see what the volume is used for.
This in combination with the method used to remove volumes when running "make clean-nuke" makes it so that theese volumes are orphaned and new ones are created and attached once the container recreated.
I sugest:
1, Finding out where theese volumes should mount and create named volumes for theese mountpoints.
2, Convert to use "docker compose down -v" which removes all attached volumes if this is possible. Im unsure how it handles when multiple compose files are used as there could be multiple different volume setups for the same container.
minigubben
commented
2 weeks ago
Both the accessy syncer and the email dispatcher docker container creates unnamed docker volumes. This itself makes it hard to see what the volume is used for. This in combination with the method used to remove volumes when running "make clean-nuke" makes it so that theese volumes are orphaned and new ones are created and attached once the container recreated.
I sugest: 1, Finding out where theese volumes should mount and create named volumes for theese mountpoints. 2, Convert to use "docker compose down -v" which removes all attached volumes if this is possible. Im unsure how it handles when multiple compose files are used as there could be multiple different volume setups for the same container.