This is not longer supported and will be deleted soon(TM)
1.7K
I do not use port forwarding on the docker host. All my docker containers have routed private or public ip addresses and public ipv6 addresses. In order to assign static ip for your container, you should create your own network. The other option is to just use the parameters for ports when running docker run command.
As of writing this, the version is 0.17.33. I have auto-update script inside. Start:
docker run -it -d --name factorio --mount='type=volume,src=factorio-mods,dst=/factorio-mods' xpuctu4/factorioworking /entry.sh
docker attach factorio
<hit c and then enter to create new save>
<ctrl-p, ctrl-q>
When started the entry scritp wait for input 30 seconds and then starts the server. The commands that can use are: c - deletes all content of the "saves" folder, and creates new save. then starts the server q - quit the script and let the docker container die w - wait for 30 more minutes <no input for 30 seconds> - starts the server - starts the server
You can omit the --mount option, but i use it to manage the mods i play from outside the container.
The server uses non-root user "factorio". In this user's home directory you can find the update script that will download the latest experimental version of the server. Please run all commands as factorio user to avoid permission bugs.
To edit server settings, update, do anything inside related to factorio:
docker exec -it factorio su-exec factorio bash
cd ~/
This command will give you bash shell with the factorio user and set your current directory to the factorio user directory.
To restart/stop the server or something like that:
docker attach factorio
[you are in the factorio console or the entry.sh script]
[do whatever you want here]
<ctrl-p, ctrl-q>
Content type
Image
Digest
Size
52.5 MB
Last updated
over 7 years ago
docker pull xpuctu4/factorioworking