github MitchTalmadge/AMP-dockerized v24
v24 - Debian 13, Java 25, Improved Performance, Simplified Setup

21 hours ago

Warning

Important: Risk of Data Loss - Read Before Updating

Due to a high risk of data loss for certain game servers (Satisfactory, ASKA, Saleblazers, and Sunkenland), it is now recommended to mount /home/amp instead of /home/amp/.ampdata. This way, directories such as /home/amp/.config are persisted when they otherwise wouldn't be.

How Data Loss Occurs

Before V24, we recommended mounting the volume /home/amp/.ampdata, which has traditionally served as the root for all AMP data (hence the name). However, some games have started to store save data in unexpected places, such as /home/amp/.config. This puts them into ephemeral storage which, by the nature of Docker, is deleted when the container is removed (such as during an update to the container). There is no way to recover this data once removed.

I hoped that I could put out an update to fix this silently, but the update process deletes the container! 😵
Instead, I will need users to back up their data before the update, then restore it afterwards.

What to Do

  • For users of ASKA, Saleblazers, Satisfactory, and Sunkenland: Please DO NOT UPDATE this image or make any changes to the container configuration until you've followed the migration guide.
  • For other users, everything will continue working without data loss but I'd still recommend doing the migration.

Follow the Migration Guide

And please, enable regular backups ❤️

What if I Already Updated?

  • I still recommend following the guide.
  • If you were not running one of the listed games, your save data should be fine. You may need to click "update" inside your game instances to re-install any missing server files.
  • If you were running one of those games, and you don't see your game saves anymore, I am sorry, but the data is gone if you do not have a backup.

Changelog

  • Updated default volume from /home/amp/.ampdata to /home/amp (see warning above).
  • Updated support for the latest AMP versions.
  • The base image has been updated from Debian 12 to 13.
  • Java 25 has been added and is the new default.
    • The image now contains all extended support versions: 8, 11, 17, 21, & 25.
    • You may need to adjust Minecraft server Java settings if your server won't boot, but personally I had no issue running various servers like Vanilla, Paper, Spigot, Forge, etc. on Java 25.
  • Image setup has been simplified based on new official setup instructions:
    • The LICENCE environment variable is no longer used. You may delete this variable.
      • This is now configured as part of the official web UI first-boot setup.
    • The MODULE environment variable has been removed. You may delete this variable.
      • "Modules" are an outdated concept that are no longer supported by AMP. All servers are now created with the ADS module, from which any other game server can be installed.
      • Existing installations will not be affected.
    • The main instance will now internally be named ADS01 instead of Main, keeping in line with the official installer. Existing installs are not renamed and will continue working.
  • Fixed reports of CPU spikes at regular intervals.
    • The pending task processor now runs every minute instead of every 5 seconds (12x decrease), per AMP recommendations.

Don't miss a new AMP-dockerized release

NewReleases is sending notifications on new releases.