I use docker-compose extensively for local development. On F24 all I had to do to make it play well with selinux was something like this: sudo chcon -Rt svirt_sandbox_file_t project_folder After updating to F25 this doesn't work anymore. Did something changed on selinux policies (besides that label been renamed to container_file_t) or I should file a bug? Specifically I cannot start a mariadb container with compose. On a related note, I opened a bug on our developer portal, since it lacks any mention on SELinux https://github.com/developer-portal/content/issues/163 ~nikos
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
