unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 48035@debbugs.gnu.org
Subject: bug#48035: Fwd: regression: “guix pack” Docker images no longer work on AWS
Date: Tue, 27 Apr 2021 09:55:40 +0300	[thread overview]
Message-ID: <YIe1bN7aPJFkr54J@3900XT> (raw)
In-Reply-To: <877dkpoz40.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

On Mon, Apr 26, 2021 at 05:16:15PM +0200, Ricardo Wurmus wrote:
> 
> 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…)
> 

On March 10th, a couple of days before your original message, docker was
updated to 19.03.15 for some security fixes. Perhaps try locally
reverting that and see if it fixes your problem.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-27  6:57 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 ` bug#48035: Fwd: regression: “guix pack” Docker images no longer work on AWS Ricardo Wurmus
2021-04-27  6:55   ` Efraim Flashner [this message]
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=YIe1bN7aPJFkr54J@3900XT \
    --to=efraim@flashner.co.il \
    --cc=48035@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).