AMP
AMP copied to clipboard
docker-ce upgrade causes running game servers to be ungracefully terminated
Operating System
Ubuntu Server 22.04.5 LTS
AMP Version and Build Date
2.6.4.2 - 20251210.2
AMP Release Stream
Mainline
I confirm that
- [x] I have searched for an existing bug report for this issue.
- [x] I am using the latest available version of AMP.
- [x] my operating system is up-to-date.
Intended Action
Upgrade the docker-ce (and related) packages through APT while an AMP instance is running (which might happen automatically at night by unattended-upgrades).
Expected Behaviour
That the instance's game server is shutdown gracefully, and then started again when the upgrade is finished.
Actual Behaviour
The game server and the AMP instance controlling it are ungracefully killed — shutdown tasks appear in neither the AMP logs nor the game server logs — the logs simply stop at the time the upgrade was initiated. The AMP instance and game server do not start back up automatically either.
Reproduction
- Install AMP on a Debian-based Linux distribution.
- Configure AMP to run its game servers inside Docker containers.
- Start any game server via AMP.
- Upgrade Docker Engine using the system package manager (e.g. via
apt upgradeor unattended-upgrades), such that the Docker daemon is restarted. - Observe that both the game server container and the AMP instance controlling it are terminated without a graceful shutdown (no shutdown tasks appear in AMP logs or game server logs; logs stop abruptly at the time of the upgrade).
- Observe that the instance does not start back up automatically.
Try creating an override for ampinstmgr.service to work around it:
systemctl edit ampinstmgr.service- Add:
[Unit]
After=docker.service
Wants=docker.service
PartOf=docker.service
[Install]
WantedBy=docker.service
systemctl daemon-reloadsystemctl restart ampinstmgr