RallyBlock/Blockland-Docker-Pelican
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
RallyBlock
2026-03-07 19:51:28 -05:00
parent 679a9f38eb
commit 90f36caaf6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -10,7 +10,7 @@ Create a custom egg in Pelican that uses `rallyblockk/blockland-pelican` as its
The image is available on Docker Hub at [rallyblockk/blockland-pelican](https://hub.docker.com/r/rallyblockk/blockland-pelican).
**Note:** Blockland works best with host networking due to UDP and Join IP behavior (see Networking section). Host network is configured in Wings (`/etc/pelican/config.yml`), not in the egg.
**Note:** If you run into connection issues, see the Networking section—host network mode may help (configured in Wings, not in the egg).
### Environment variables
| Name | Type | Default | Description |
@@ -34,7 +34,7 @@ The image is available on Docker Hub at [rallyblockk/blockland-pelican](https://
| WINEDEBUG | string | -all | Controls how much logging Wine does to the console (default hides everything)
### Networking
Blockland uses UDP and can be finicky with Docker bridge networks. For the most reliable results, configure Wings to use host network mode in `/etc/pelican/config.yml` (see [Pelican's optional config docs](https://pelican.dev/docs/wings/optional-config/)). Host network is Linux-only and removes Docker network isolation—use with caution on shared nodes.
Blockland uses UDP. The original image recommended host network mode for reliability, but many users run fine with Pelican’s default bridge network. If you have connection issues (players can’t join, server not visible, etc.), try configuring Wings for host network mode in `/etc/pelican/config.yml`—see [Pelican’s optional config docs](https://pelican.dev/docs/wings/optional-config/). Host network is Linux-only and removes Docker isolation; use with caution on shared nodes.
### Volumes
Pelican mounts each server's data directory at `/home/container` (the working directory). Files there are persisted as the server's storage. The container runs as UID/GID 1000—Pelican typically handles permissions, but that can cause issues if something is misconfigured at the node level.