- Dockerfile 41.9%
- TypeScript 30.9%
- Shell 27.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
Publish OCI Images / matrix-generator (push) Successful in 7s
|
||
| .forgejo/workflows | ||
| examples/starter | ||
| .gitignore | ||
| Containerfile | ||
| entrypoint.sh | ||
| fetch.ts | ||
| README.md | ||
Containerized: Factorio
The easiest way to run factorio in a container.
Getting Started
Versioning
stable: Latest stable versionexperimental: Latest experimental version2.x.x: Specific game version from2.0.76onwards
This project runs automatic hourly updates.
Run container
podman run forgejo.fpallas.dev/containerized/factorio:stable \
-d \
-v "./data/saves:/opt/factorio/saves" \
-v "./data/config:/opt/factorio/config" \
-p "34197:34197/udp"
Compose container
services:
factorio:
image: forgejo.fpallas.dev/containerized/factorio:stable
volumes:
- ./data/saves:/opt/factorio/saves
- ./data/config:/opt/factorio/config
ports:
- "34197:34197/udp"
Configuration
Please refer to the official factorio wiki and example configs to configure the server.
Place your configurations in a directory and mount it under /opt/factorio/config.
Savegames
When no save is provided, the server will automatically generate a map with default settings at first startup.
The server places all savegames, including autosaves under /opt/factorio/saves.
Uploading a save
The server always loads the _autosave1.zip at startup. To start with your own save, or replace the existing save, simply rename your save to _autosave1.zip and place it in the mounted save folder.
Advanced Usage
The focus of containerized is on simplicity. This allows us to keep images close to the original application. For more advanced use-cases refer to other containers instead.