You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current documentation focuses on how to configure/start the server services, and largely leaves it up to the reader to figure out how they want to configure/connect clients. As pointed out in this blog if you use the example docker-compose.yml file from GitHub it doesn't expose any ports externally.
While the official documentation recommends using --network="host" which should allow external clients to "just work", since this repository is now public it makes sense more people will start referring to the more concise examples/ so we should make those more clear and consider covering a few common use cases. For example:
network_mode: "host".
network_mode: "bridge" with port mapping.
network_mode: "bridge" without port mapping and a container on the same bridge network able to access BeeGFS.
The text was updated successfully, but these errors were encountered:
Current documentation focuses on how to configure/start the server services, and largely leaves it up to the reader to figure out how they want to configure/connect clients. As pointed out in this blog if you use the example
docker-compose.yml
file from GitHub it doesn't expose any ports externally.While the official documentation recommends using
--network="host"
which should allow external clients to "just work", since this repository is now public it makes sense more people will start referring to the more conciseexamples/
so we should make those more clear and consider covering a few common use cases. For example:network_mode: "host"
.network_mode: "bridge"
with port mapping.network_mode: "bridge"
without port mapping and a container on the same bridge network able to access BeeGFS.The text was updated successfully, but these errors were encountered: