@Greelan has fully redesigned the Docker images that AMP uses from the ground up. These new images are being pushed out shortly. They will automatically apply the next time you update your instance. You won’t see a notification of this since it’s more of a background thing AMP handles. You should not see any negative impact from the changes, but we wanted you to be aware so you can report any oddities you may find.
1 Like
For further context:
- The new images will be applied to Generic module-based instances on update of those instances.
- Minecraft Java and Rust module instances (and legacy FiveM/RedM instances) won’t get the new images applied automatically until AMP’s code is updated in a later release. They can be manually updated in the meantime by editing the instance’s container settings - click on the pencil icon on the instance - to specify the applicable image:
- Minecraft Java:
cubecoders/ampbase:java-lts - Rust:
cubecoders/ampbase:debian
- Minecraft Java:
- Further code changes are pending in AMP around the transition to these images, such as:
- Making them selectable in the container image dropdown for individual instances
- Updating AMP’s installation script so that it also installs and configures Docker on ARM platforms. The new images are (where relevant) now also built for ARM
- Adding automatic dangling image pruning so that disk space usage is minimised. In the meantime, you can do this manually with
docker image prune -f
After update of your instances, you may not see the image name being shown correctly in the instances’ container settings. A restart of ADS will address this.
For Wine-based instances in particular, you may have an issue starting the server after update to the new image, if the Wine prefix for the instance is an older one. This will normally be solved simply by updating the server.
Details of the new images are here.
1 Like