unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 48035@debbugs.gnu.org
Subject: bug#48035: Fwd: regression: “guix pack” Docker images no longer work on AWS
Date: Mon, 26 Apr 2021 17:16:15 +0200	[thread overview]
Message-ID: <877dkpoz40.fsf@elephly.net> (raw)
In-Reply-To: 87tupgndrw.fsf@elephly.net


Hi Guix,

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…)

-- 
Ricardo




       reply	other threads:[~2021-04-26 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87tupgndrw.fsf@elephly.net>
2021-04-26 15:16 ` Ricardo Wurmus [this message]
2021-04-27  6:55   ` bug#48035: Fwd: regression: “guix pack” Docker images no longer work on AWS Efraim Flashner
2021-04-27  7:48     ` Ricardo Wurmus
2021-04-28 21:29   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dkpoz40.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=48035@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).