Closed rykugur closed 3 years ago
Thank you for this complete description of your problem.
I have never had any problems communicating with Steam. I'll check it out quickly.
I made some updates to make this image more usable. Could you test the new version by updating your configuration file with 0.2.2 tag or pulling the latest.
Documentation is also updated with 2 networks mode: bridge and host.
I test your configuration without LGSM_SERVER_CONFIG environment and the server start without a problem. Maybe you have a network connection problem. Closed ports or something like this.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug When I start the server via docker-compose (file pasted below), I'm getting the following errors in my server-console.txt file:
No world is ever created.
If I run the container directly (not using docker-compose) it appears to work without issue; a world is created on disk.
To Reproduce Steps to reproduce the behavior:
docker-compose -f docker-compose.yml up
Expected behavior Server starts, world is created.
Actual behavior Server doesn't start, docker container remains running, world is not created.
Screenshots N/A
Additional context Here is my
docker-compose.yml
file (mostly copy/pasted from another issue on this github to address the invalid IP bug, which still seems to be an issue on 0.2.1/latest):I'm far from a docker whiz, but pretty sure it's telling me that the container is unable to communicate with steam. Might be wrong. Definitely odd that it works via
docker compose
though?