Public | Automated Build

Last pushed: 6 days ago
Short Description
Factorio headless server
Full Description

Factorio Docker Container

Docker tags:

Tag Factorio Version Description Release Date
latest 0.15.40 Factorio headless server stable release 2017-12-04
experimental 0.16.30 Factorio headless server experimental release 2018-03-12
release-0.15.40 0.15.40 Factorio headless server stable static release 2017-12-04

AS OF 2017-09-28: For security/attack surface reduction the container is configured to run the Factorio headless server with an internal user & group factorio having a pre-set UID & GID of 999.
The container will attempt to adjust permissions on mapped volumes and data to match before dropping privileges to start the Factorio server processes.
If the container is being run with a different Docker --user setting permissions may need to be fixed manually.

IE: chown -R 999:999 /DATA_VOLUME/factorio/{config,mods,saves}

A custom UID and GID can be configured for the container internal factorio user and group. For more information see the "Environment variables" section in this document.

Always stop the existing container and make a VERIFIED backup copy of your Factorio data before installing newer images.
Make a backup of your v0.14.X saves before upgrading to v0.15.X. A lot has changed and may break existing maps/saves.


The container exposes three volumes:

  • /opt/factorio/config - Factorio headless server config files
  • /opt/factorio/mods - Factorio mods default directory for non-standard add-ins
  • /opt/factorio/saves - Factorio save/map file storage location

The container exposes two ports:

  • 27015/tcp: Factorio RCON port
  • 34197/udp: Factorio default server port

The most basic way to run this container:

$ docker run --name factorio -d \
    -p 34197:34197/udp \

Recommended run command line -

Have the container store the config, mods and saves on a local file-system or in a specific, known data volume (recommended for persistence and troubleshooting) and expose the RCON port for admin:

$ docker run --name factorio -d \
    -p 27015:27015 -p 34197:34197/udp \
    -v /DATA_VOLUME/factorio/config:/opt/factorio/config \
    -v /DATA_VOLUME/factorio/mods:/opt/factorio/mods \
    -v /DATA_VOLUME/factorio/saves:/opt/factorio/saves \

Logs are available directly from the running container, IE: "docker logs factorio"

Environment variables:

Variable Default Description
DEBUG false Set to true for extra container verbosity for debugging
FACTORIO_RCON_PASSWORD unset Specifiy the RCON password
FACTORIO_OPTS unset Add custom command line options to factorio server executable at runtime
FACTORIO_GID 999 Specifies the GID for the container internal factorio group (used for file ownership)
FACTORIO_UID 999 Specifies the UID for the container internal factorio user (used for process and file ownership)
RUNAS_UID0 false Set to true to force the container to run the Factorio server process as UID=0 (root) - NB/IMPORTANT: running with this set to "true" is insecure

Docker Compose:

Example basic docker-compose.yml file

During the first launch of the container the server-settings.json and map-gen-settings.json config files will be populated with the Factorio sample/defaults if they don't already exist. It is highly recommended to edit these files and relaunch the container afterwards or provide pre-setup copies in the config directory prior to first launch. The config sample files are available in the headless server tar.gz file in the "data" folder. The container will also generate a default map / in the saves folder if one is not found on launch.

The RCON password can be set via the FACTORIO_RCON_PASSWORD ENV flag or loaded from /opt/factorio/config/RCON.pwd each time the container is started. If the FACTORIO_RCON_PASSWORD ENV var is not set or the RCON.pwd file is not present a random RCON password will be generated and saved in /opt/factorio/config/RCON.pwd. The active RCON password can also be found at the start of the container log file at each launch.

Docker Pull Command
Source Repository