komga icon indicating copy to clipboard operation
komga copied to clipboard

ubuntu 25.10 removed /etc/timezone

Open gen-angry opened this issue 5 months ago • 1 comments

Steps to reproduce

Hello,

I have a podman container set up with using /etc/timezone as a bind mount which has worked fine. No issues with ubuntu 24.04, 24.10, 25.04.

I just upgraded to ubuntu 25.10 which has removed it apparently according to this: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2103839

So now when starting the container in 25.10, it now prevents it from starting:

Nov 07 08:26:06 202server komga[9739]: Error: statfs /etc/timezone: no such file or directory

As a workaround, I added environment variable TZ=America/Toronto to the container file and removed the mount which allowed it to work again. But I figure I'd give a heads up saying that this mount method no longer seems to work with the latest ubuntu releases and to provide a workaround for those who run into this issue and might come on here to find a solution.

The installation documentation could probably use a note as well. https://komga.org/docs/installation/docker

Expected behavior

Container to load.

Actual behavior

Container crashes with error.

Nov 07 08:26:06 202server komga[9739]: Error: statfs /etc/timezone: no such file or directory

Logs

No response

Komga version

v1.23.5-master

Operating system

ubuntu 25.10

Installation method

other (please provide more details below)

Other details

podman container using docker information.

Acknowledgements

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

gen-angry avatar Nov 07 '25 13:11 gen-angry

i cannot reproduce the container not starting. Tried with a simple docker run gotson/komga and it starts fine. /etc/timezone is not required for the container to start.

Maybe that's a Podman issue ?

gotson avatar Nov 10 '25 01:11 gotson