Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I’m using “guix pack”-generated Docker images on AWS ECS.  On June 17,
> 2020 I generated and uploaded an image that works fine.  According to
> AWS this image has this manifest type:
>
>    application/vnd.docker.distribution.manifest.v2+json
>
> Today I generated a new image that does not work.  It cannot be opened
> by ECS; it cannot find /bin/sh, which exists.  The manifest type is
> now
> recognized as
>
>    application/vnd.oci.image.manifest.v1+json
>
> It also now detects an “Artifact media type” and prints it as
>
>    application/vnd.oci.image.config.v1+json
>
> I’d very much like to push a newly generated image.  Is there a way to
> generate the image as it was done in the summer of 2020?
>
> Note that both these images appear to work “fine” with a local Docker
> installation (i.e. when run with “docker run”).  (When running /bin/sh
> in the container interactively it appears to freeze whenever I try to
> actually run a command, but perhaps I’m just holding it wrong…)

The Git log of (guix docker) and (guix scripts pack) doesn’t show
anything suspicious.

Could you try generating an image with ‘guix pack’ and feeding it to
Docker using Guix’ Docker service in a VM?  Attached is an OS that I
used previously to test Docker things.  (You need to run with ‘-m 8192’
or similar so that when you run ‘docker load -i
/gnu/store/…-docker-pack.tar.gz’ the whole VM disk fits into RAM.)

If you used ‘-S /bin=bin’, /bin/sh in the image is a symlink to
/gnu/store/…-bash/bin/sh, an absolute file name that’s only valid within
the image.  Perhaps Docker is confused by that like Singularity is/was.
In that case, try changing ‘guix pack’ so it produces relative symlinks
as it already does for the ‘singularity’ backend.

HTH!

Ludo’.