Seems to be container-selinux.Partial (There is considerable informational disclosure.) Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this.
The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged. Matching error messages can be seen using journalctl, so it is an SELinux problem. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared. It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts. #docker attach UMS # Still unintentionally stops container when done inspecting.įor detailed logs in the terminal: echo -e '\nlog_level=ALL' > UMS.conf docker cp :/var/log/UMS/root/debug.log. Investigating Problems/Issues General docker ps -a Profile folder containing UMS.conf VOLUME /profileĮxpose/forward these ports from the host: 1044, 5001, 9001. v "$HOME/.config/UMS":/root/.config/UMS \ Container Setup set rootDir "/home/UMS/.config/UMS" įor file in "UMS.conf" "WEB.conf" "ffmpeg.webfilters" Mount storage to host and link into that directory, probably read-only. Sudo chcon -t svirt_sandbox_file_t /srv/UMS Fedora Linux Preparationįor operating system support and service packages. Understand what they do, and ignore or customize as necessary. Some of these steps may not apply to your installation.
0 kommentar(er)
