859
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
====Networking====
====Networking====
See Issues and other comment further down re host/bridged networking.
Docker attempts to guess what network to use and sets a bridged interface for it.
Docker attempts to guess what network to use and sets a bridged interface for it.
* How to interact with localhost PAM or LDAP from within a container?
* How to interact with localhost PAM or LDAP from within a container?
I think that you can access localhost services by adding
I think that you can access localhost services by adding:
--net="host" to docker run
--net="host" to docker run
This means any services on the docker container are equally valid 'localhost' services accessible from the server itself so you need to ensure the server is properly firewalled.
This means any services on the docker container are equally valid 'localhost' services accessible from the server itself so you need to ensure the server is properly firewalled. See Issues below.
* Many more...
* Many more...
* Get the [https://github.com/shipyard/shipyard shipyard GUI] going
* Get the [https://github.com/shipyard/shipyard shipyard GUI] going
* A LOT more ;-)
* A LOT more ;-)
==Issues==
You will find that if you use 'host' networking docker will set /sys as Read Only and you will get an error with the raid_check as per this bug
https://bugs.contribs.org/show_bug.cgi?id=10660
If you don't use host networking, you use the internal IP address set with docker, but this address is unknown as a local network to SME and it will block any queries emanating from the container. I am looking at this with the contrib.
[[Category:Containers]]
[[Category:Containers]]
[[Category:Containers:Docker]]
[[Category:Containers:Docker]]
