System Information
| Field | Value |
|---|---|
| Operating System | Linux - CentOS Stream 10 on x86_64 |
| Product | AMP ‘Proteus’ v2.8.0.8 (Mainline) |
| Virtualization | VMware |
| Application | Application Deployment |
| Module | ADSModule |
| Running in Container | No |
| Current State | Indeterminate |
Problem Description
Issue
A game server instance on my amp server was running fine yesterday, but after rebooting the instance today so that the new directory for backups I linked would show up inside the instance’s File Manager, it started giving me the error that:
“Current user (amp) isn’t part of the docker group. You can fix this by running `usermod -a -G docker amp` as root. If you’ve already added the user to the group you may need to restart AMP or possibly reboot the system.”
When I tried adding amp to the docker group manually from the host server CLI itself, it said the group does not exist.
Reproduction Steps
- boot host server
- amp starts automatically
- attempt to start instance
UPDATE:
After checking more logs the error was caused by the permissions on the symlink file. It was owned by root, and amp was trying to change ownership of it and failing. Not sure why it would then throw the docker group error it did. Issue is now resolved, so this is more of a bug report now and I have moved it to feedback.