3 ms·
From the docs (wtf?): > Please disable Selinux or any firewalls before configuring containers, networks, storage and cluster services. They can interfere in un
by irq-1 8y ago
From the docs (wtf?):
> Please disable Selinux or any firewalls before configuring containers, networks, storage and cluster services. They can interfere in unpredictable ways. Once configured services are working you can add the relevant exceptions and enable them again.
- tobbyb 8y agoUnfortunately Selinux can interfere with processes in weird ways without clear messages to end users. When a container starts networking devices are created, if using layers or btrfs/zfs overlays or snapshots may be created, bind mounts activated. There is a lot of potential for permission issues. Similarly when creating overlay networks ports across systems need to be open. The idea behind this is users can ensure the functionality is working as desired before enabling firewalls and other security features so they can debug issues effectively. We have tried to provide a lot of documentation so new users can get started and get comfortable with containers and networking. Often users get discouraged if even after following the docs they run into issues.
- unixhero 8y agoMakes sense...
- cjhanks 8y agoThere are different layers of security. Presumably, when your hardware is provisioning a new operating system, it is protected by a Layer3 firewall. But, yeah - people tend to only skim the manuals.