-
Notifications
You must be signed in to change notification settings - Fork 107
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
Warning on Upgrade 1.1.0 to 1.2.1 #417
Comments
It looks like you need to clear the cache, maybe when restarting the docker we are not doing it correctly? |
Hello @temp is it possible for you to check the master branch version. I would like to know if our fix has solved this problem. I will be grateful for your feedback. Thanks 😉 |
@akondas uh, I already did a manual clear cache, und it worked fine. Since I'm already on 1.2.1, I'd have to downgrade to 1.1.0 again... Any other volunteers? :-D |
No downgrade needed. Thanks, we'll test it ourselves. |
I can restart the stack, if this is sufficient. Haven't restarted it after the cache-clear. I'll try. |
Restart worked fine, no warnings. |
When I do a docker-composer up I can see:
Didn't see anything related in the UPGRADE-docs, did I miss something?
The text was updated successfully, but these errors were encountered: