-
-
Notifications
You must be signed in to change notification settings - Fork 26
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] Unable to apply the latest version r1720 in unraid #44
Comments
Get the docker run command unraid used to create the container. |
NexusEFR
changed the title
[BUG] <title> Unable to apply the latest version r1720 in unraid
[BUG] Unable to apply the latest version r1720 in unraid
Aug 26, 2024
Sorry I don't understand, I don't know how to proceed with your message. Thank you in advance. Best regards |
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
Hello, great contribution to unraid, I have it in production and I can't put the latest r1720 version. When I enter the console it still appears as the r1605 and that I have the option to download it. But I've already applied the last tag since unraid, and on the console I get that I have the r1720. What can happen? I don't know what else to do, I even edited the nginx .conf files from the sample. I show screenshots of everything. Thank you very much! Best regards
Expected Behavior
After applying the update in the Unraid CA Store, the latest version is not set on the web.
Steps To Reproduce
docker unraid
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: