-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
embystat:beta container fails to start #1745
Comments
I released beta.30 yesterday. Can you try again to spin up the container? |
It works with the most recent beta (pulled a few minutes ago) but only if I remove user: $PUIDN:$PGIDN when .env is loaded this becomes user: 99:100 |
I'm not sure that Embystat is using that user property. The next big update is to make the runtime and startup more robust, so I'll try to include the runtime user correct as well. |
I removed the user property for now. Embystat starts now and seems to work with the latest beta. However, it doesn't seem to be storing the data in the /app/config folder? I mapped /app/data instead and see the logs and usersettings.json in there, but where is the database info stored? I've scanned my jellyfin server but no embystat database exists anywhere that I can find, either in my mount folders or in a docker volume. |
True, it seems I had some bugs that the data/logs/config folders were not correctly used. I'm currently working on a fix for that. Thanks for letting me know! |
Bug report
Describe the bug
Getting the below when I try to start a uping/embystat:beta container
To Reproduce
Steps to reproduce the behavior:
System (please complete the following information):
Additional context
Docker Compose:
The text was updated successfully, but these errors were encountered: