-
-
Notifications
You must be signed in to change notification settings - Fork 549
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
Newest docker update doesn't start #3099
Comments
I've got the same issue. |
1 similar comment
I've got the same issue. |
I mounted the following and then unmounted it:
That seemed to clear out the issue. I'm guessing if I'd used console to login and clear the folder, it would have done the same. |
I will revert the change befefore more people get affected, it's not really important, was just a nice to have |
Interesting, I can't seem to replicate the issue. @marmata @jhuang0 @casimpunkt, can one of you share your configuration files so I can try to replicate the issue and debug the problem? |
I am also having this issue on 1.5.17, interestingly enough. Not sure if I ever had 1.5.16 so it is unclear if it was a problem that persisted from 1.5.16 or that newly appeared with 1.5.17. Note that I am running tandoor via DockSTARTer, with an Nginx setup. docker-compose.yml
.env
Also, suggestions for a workaround would be greatly appreciated. At first I was happily tinkering away to find a solution, but it occurred to me that I don't have my database backed up properly and now I'm really nervous about losing my recipes. Can't test any backup solutions till I can get an instance running properly again. |
Try deleting the contents of staticfiles and restarting the container. |
Sure, here's my docker compose:
and my .env
|
Deleting the staticfiles folder seems to work. I have a feeling the only reason it didn't work for me on 1.5.17 was because updating the image didn't fix whatever was wrong with the staticfiles. Anyway, happy to provide any more information to help replicate the issue if possible. |
It appears that the root of the problem lies in Compose's behavior of reusing existing images, which have already moved the necessary files. Consequently, this prevents any further movement of files. While platforms like K8S generate containers from scratch, mitigating this issue, other platforms like Compose are affected. |
Tandoor Version
1.5.16
Setup
Docker / Docker-Compose
Reverse Proxy
Caddy
Other
No response
Bug description
Since updating to 1.5.16 I only get 500 error when connecting to Tandoor. By looking at the logs it has probably been introduced by this commit. Any way to put the files back where they should be? Any command I can use inside the docker? Thanks!
Relevant logs
The text was updated successfully, but these errors were encountered: