Closed ahmaddxb closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The same issue happens for me. It can be that this only occurs in headless systems.
This is also happening on my UnRaid server once I updated to 6.10.1. This is the only Docker that is having this issue. I even removed it, deleted the original folder out of the appdata folder, and it is still happening after reinstalling. So I'm not sure what the issue is. This is my favorite file manager on my UnRaid Server, so I hope this can be figured out. I was thinking it was a permission issue, but I honestly don't know enough to make that a definitive answer. Any help would be welcome. Thanks.
This is also happening on my UnRaid server once I updated to 6.10.1. This is the only Docker that is having this issue. I even removed it, deleted the original folder out of the appdata folder, and it is still happening after reinstalling. So I'm not sure what the issue is. This is my favorite file manager on my UnRaid Server, so I hope this can be figured out. I was thinking it was a permission issue, but I honestly don't know enough to make that a definitive answer. Any help would be welcome. Thanks.
I had the same problem running this container from Unraid. What I needed to do is to toggle the container as privileged. That solved the issue for me.
o
That fixed it for me, thanks. The only one I couldn't get was DoubleCommander, but this fixed it right up. Thanks. Any thoughts as to why updating would do this? I never had this problem before.
Ok thanks I will give it a try, hopefully that solves it for me too.
Edit: It is working now running with privileged: true
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Setting privileged: true worked for me on unRAID 6.11.3 as well.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Expected Behavior
Webui to load doublecommander
Current Behavior
Steps to Reproduce
1. 2. 3. 4.
Environment
Docker version 20.10.14, build a224086 docker-compose version 1.29.2, build unknown
NAME="Ubuntu" VERSION="20.04.4 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.4 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
OS: Ubuntu 20.04.4 LTS CPU architecture: arm64 How docker service was installed:
Command used to create docker container (run/create/compose/screenshot)
docker-compose
Docker logs