-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Startup fails: Failed to close file descriptor for child process (Operation not permitted) #22
Comments
Here is the Digikam log: rdpkeybControl: what 1 |
Because the original poster ignored the issue template when they opened it. |
Yes I'm guilty...sorry about not following templates...I'm a first time
poster...my digikam is still down...too bad...it was filling my
needs...perhaps I can take another shot logging this issue...
…On Sat., Apr. 2, 2022, 5:12 a.m. j0nnymoe, ***@***.***> wrote:
Because the original poster ignored the issue template when they opened it.
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYJLMA3ZDXNCALCOB23HOSDVDATTDANCNFSM5REOH5WQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
can you reopen please, so we have the full trail? here we go Expected Behaviour Current Behaviour Steps to Reproduce Environment OS: How docker service was installed: Command used to create docker container (run/create/compose/screenshot) network_mode: host
mem_limit: 1500M
mem_reservation: 256M
version: "2.2" network_mode: host
mem_limit: 1500M
mem_reservation: 256M
Docker logs |
Comment deleted |
1 similar comment
Comment deleted |
If anyone came across the same problem, a workaround is to run the container with the flag |
Thanks, that worked … I've read a few times and don't get the implications completely, but it's internal, and it works, so I'm good with that. Thanks a lot @nathabonfim59 |
Had digikam working beautifully in docker unraid.
Then went headless and rebooted (not sure if this is red herring or not).
Now after serval attempts to re-install (and killing appdata) the startup will not run (error in title).
Where can I find help with this issue?
Could it be database related?
Expected Behavior
Current Behavior
Steps to Reproduce
Environment
OS:
CPU architecture: x86_64/arm32/arm64
How docker service was installed:
Command used to create docker container (run/create/compose/screenshot)
Docker logs
The text was updated successfully, but these errors were encountered: