Container creates Docker volume for /tmp

[dathbe]

Steps to reproduce

Run container

Expected behavior

Either
(1) container will not try to create a volume for the /tmp folder (ideal)
or
(2) the documentation mentions mapping or binding /tmp to a host folder or Docker volume to avoid repeated creation of an unnamed volume very time the container is destroyed and recreated.

Actual behavior

Unless /tmp is explicitly bound or mapped, an unnamed volume is created. New volumes created each time the container is removed and recreated.

Logs

No response

Komga version

1.23.6

Operating system

Debian 12

Installation method

jar

Other details

Docker-compose

Acknowledgements

• I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[gotson]

/tmp is required, and it's declared here

komga/komga/docker/Dockerfile.tpl

Line 46 in e6560e0

VOLUME /tmp

just map it to host if you need to

[Thilas]

I kind of agree that the current state is not ideal, especially because by default, we end up having dozens of unused and unmapped volumes.

@gotson, I understand that /tmp is required but as mentioned by @dathbe, either it shouldn't be declared as a volume (what's the problem in using the container's /tmp?) or it should be documented, especially for those who would like to map it on the host.

Thank you.

[gotson]

i don't understand the problem tbh, i don't have dozens of unused/unmapped volumes myself.

if someone can provide more details on the symptom, the best practice, and what other apps do, then we can evaluate changing it.

[gotson]

quickly checked on that, this was an old recommendation from Spring Boot, which is not recommended anymore. Will remove the anonymous volume.

[Thilas]

thanks!