-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
[BUG] Runtime update not supported #411
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Oops, those should be |
My bad, I've pushed a fix, should build in the next few minutes |
Thanks for the super fast response, that did the trick! 👍🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
Since the
1.41.0.8994-f2c27da23-ls239
release which adds support for running the container in read-only mode, the container is no longer able to self-update despiteVERSION=latest
being set and the container being in read-write mode.It would appear that the check is faulty and in fact always blocks updating unless
LSIO_READ_ONLY_FS
andLSIO_NON_ROOT_USER
are both defined, which I guess they shouldn't be unless the container is actually running in read-only mode.The
1.41.0.8994-f2c27da23-ls239
release prints the following line instead of updating:Downgrading the container to
1.41.0.8994-f2c27da23-ls238
fixes the issue:Expected Behavior
When running the container in read-write mode, and
VERSION=latest
is set, and a plex-pass update is available, the container should self-update as normal.Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: