OS Name/Version: Ubuntu 22.04.2 LTS
Product Name/Version: AMP 2.4.3.6
Problem Description:
After migration docker won’t start and instead returns error 127.
Recent Log:
[...]
Already up to date.
AMP is up-to-date.
88d103555f93e00bf83f581e3cb848834ff74b3a0467a269e2e1cfbe9c3e1142
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/ampstart.sh": stat /ampstart.sh: no such file or directory: unknown.
fc2892ba718b92beed1b3767ae939b917fc7c6489f1f498d0a9589e98fef4b8e
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/ampstart.sh": stat /ampstart.sh: no such file or directory: unknown.
Further Important Information:
AMP is running inside a Linux Container (LXD) with nesting enabled and has worked fine previously.
Steps to reproduce:
- Create backup of the LXD-Container which contains AMP
- Restore said backup
- Sometimes docker instances no longer work
Solution:
- Login into said LXD-Container as root
- The following step might irreversably destroy other docker containers in the LXD-Container; AMP Instances are not affected by this, since their data is stored somewhere else. But this step is required for fixing the issue.
- Clear all docker containers and images, even existing:
docker system prune -a - Redownload the base images:
docker pull cubecoders/ampbase -a - restart the LXD-Container
- Docker should now be working again