Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container fails to properly start when defining custom configuration on podman #584

Closed
catgirlcataclysm opened this issue Jan 5, 2025 · 3 comments
Labels
Milestone

Comments

@catgirlcataclysm
Copy link

Whenever I attempt to define a custom configuration file (as shown in the documentation) the container will refuse to start and instantly crash with this error:

- 131671049818080 [MAIN] locale set to 'C.UTF-8;C;C;C;C;C'

Caught std::exception: filesystem error: cannot create directories: Invalid argument []

I have tried starting with this command:

podman run --name lms --entrypoint '["/usr/bin/lms", "/var/lms/lms-custom.conf"]' -p 5082:5082 -v /home/kaitlyn/music/tracks:/music:ro -v /home/kaitlyn/music/lms:/var/lms:rw epoupon/lms

and this command:

podman run --name lms -p 5082:5082 -v /home/kaitlyn/music/tracks:/music:ro -v /home/kaitlyn/music/lms:/var/lms:rw epoupon/lms /var/lms/lms-custom.conf

I have yet to be able to get it to start though, and the moment I start it without defining a custom configuration it starts just fine.
I have also tried with all of the lms volumes as rw for all users (chmod 777), to no avail.

Any help would be greatly appreciated!

@epoupon
Copy link
Owner

epoupon commented Jan 5, 2025

Hello!
What did you put in the custom conf file? Would you mind to share it?

@catgirlcataclysm
Copy link
Author

well.... this is incredibly embarrassing and honestly quite stupid.
i downloaded the config from the repo and edited it, but somewhere along the line, the config file got wiped and became an empty file....

i redownloaded it and edited it again, and now it works flawlessly.
Apologies again, lol.

@epoupon
Copy link
Owner

epoupon commented Jan 5, 2025

No problem!
But LMS should fall back on proper default values, and it looks like it is not the case

@epoupon epoupon reopened this Jan 5, 2025
@epoupon epoupon added this to the v3.63.0 milestone Jan 5, 2025
@epoupon epoupon added the bug label Jan 5, 2025
@epoupon epoupon closed this as completed Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants