Repository files navigation

An image brought to you by /r/openttd

Built from OpenTTD source to provide the leanest, meanest image you'll come across for putting trainsets in containers.

A workaround to use existing game folder locations, if present, was added. New installations of the container will use/config by default - and whilst it is recommended to migrate when possible, this provides backwards compatibility.

The location of saved games / content was moved back to/config as originally intended. This incorrect functionality has been present for quite some time, but is now fixed.

This may well break existing installations. If it does, move the contents of{config}/.local/share/ to{config} - done correctly, your existingopenttd.cfg andsave directories (among others) should exist in/config in the container.

The CI system will automatically build the current latest versions at 3AM every day. This is a little hacky, but it does mean we get new builds within 24 hours of release.

You can find the images at the following locations:

Please prefer the Github Container registry for new deployments. It's 100% compatible with your Docker installation.

Images are built forAMD64 (x86_64, i.e 64bit PC) andARM64 (modern ARM, i.e Raspberry Pi 3 running 64-bit OS).

If you need an architecture not listed above, please raise an issue.

docker run -d -p 3979:3979/tcp -p 3979:3979/udp redditopenttd/openttd:latest

The container is set by default to start a fresh game every time you restart the container. You can, however, change this behaviour with theloadgame envvar:

-e "loadgame={false|last-autosave|exit|(savename)}"

where:

• false: standard behaviour, just start a new game
• last-autosave: load the last chronological autosave
• exit: try to load autosave/exit.sav, otherwise default to a new game
  • Please make sureautosave_on_exit = true in youropenttd.cfg for this to work.
• (savename): full name of a save file in config/saves

You'll probably want stuff to be persistent between container rebuilds, so we've got the/config volume for exactly that purpose.

-v /home/{username}/.openttd:/config:rw

The easiest way to play with NewGRF's is to first download and configure them how you want on a local machine with a GUI. Then in the config/ directory copy the folder from local machine named content_downloaded to the server. Next update the openttd.cfg file from your local machine, this is to ensure that when you create a new server your NewGRF settings will be copied across.

docker run -it -p 3979:3979/tcp -p 3979:3979/udp -v /home/{username}/.openttd:/config:rw -e "loadgame=game.sav" redditopenttd/openttd:latest

This will start a server with the console accessible due to-it in the command line, to run in the background use-d.

Replace all of thedocker commands in thedocker section withpodman. If you're having issues, please raise an issue.

Because OpenTTD is quite heavily stateful, we have written some handy helper containers for you to use as init containers and sidecars. Please see theopenttd_k8s-helpers repo for more information.