<rekado>I may be wrong but it sure seems that our generated Docker images no longer work on AWS.
<rekado>it says: “CannotStartContainerError: ResourceInitializationError: failed to create new container runtime task: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
<rekado>that’s a bit odd, because /bin/sh exists (as a symlink) and a much older Docker image that we generated still works
<civodul>rekado: could it be that it's an absolute symlink to /gnu/store and the thing tries to resolve it outside the image?
<civodul>Singularity had that problem so we take special measures there
<civodul>see uses of 'relative-file-name' in (guix scripts pack)