-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
Docker container crashed with version 2.4.x #1947
Comments
I just want to conform @geimist bug issue. (2.4.1 untested, but it seems the same problem) |
I'm not exactly sure why this happens, as we deployed with Docker on our ANCT instance without issue, and I can run it locally with docker compose, but the error message seems the same as the one we hit recently, and fixed in master: We'll deploy a new version including this fix this week, let's see if it fixes your issue to! |
Unfortunately, the problem still exists with version 2.5.1: 🙁
|
@geimist 😞 It appears that you're hitting this limit which raises that issue. Do you have a way to bump that limit here within your container prior to (re)run the |
I think I need support for this. |
Indeed that's not trivial and I probably have to release a dedicated image to test. By the way, do you have/set custom statics for your instance? |
No, not to my knowledge. |
Can you confirm this is fixed with 2.5.1 image ? |
I had already written about this above:
|
Oops, sorry! Back from holidays, I've missed some notifications :p
This "All" file (which comes from our logs) is still a mystery to me. Let's maybe make |
I am chipping in. I am still having the exact same issue. Here is my compose:
Both containers start up fine, but the app container then keeps throwing:
My "hunch" is that the umap.conf file I created empty needs to contain real default settings at init? But I couldn't find any reference to this, so I just kept it empty with #placeholder as comment and started it up. |
New Docker image released today, with a few fixes related to Docker, could have a try with 2.6.1 ? 🤞 |
Great, it works perfectly. |
I just want confirm, that the Docker image upgrade 2.3.1 -> 2.6.3 works! |
Yay! |
Describe the bug
If I use the Docker image >= 2.4, the container does not start successfully. With the 2.3.1 image, the container starts as usual.
Have I overlooked a necessary adjustment?
container log
(Lines in the log are sorted from new to old)Additional context
Installed at Synology DSM 7.2 (Container Manager)
The text was updated successfully, but these errors were encountered: