Sunil Mohan Adapa e7e1a6b41d
nextcloud: Drop network namespacing in container, use host network
- This is not ideal and reduces security. However it simplifies quite a bit of
setup.

- Services on the host network are already exposed to the container (however,
they could easily be protected with firewall rules).

- Container has full access to external networks already. So this part does not
change.

- This setup would be at par with how other services run on FreedomBox right
now. We can think of generalized solution for all the apps later.

- FirewallLocalProtection for the single service the runs in the container works
as usual without change.

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
2024-05-06 17:14:23 -04:00
..
2024-05-02 21:46:11 -07:00
2024-04-22 21:03:15 -04:00
2024-05-02 21:45:25 -07:00
2020-02-19 14:38:55 +02:00
2024-03-16 09:17:35 +02:00
2024-05-02 21:46:11 -07:00
2024-03-16 09:17:35 +02:00