2021-01-09 08:06

Images built with buildah stopped working on AWS Fargate


Since yesterday I'm unable to run images built with buildah on AWS Fargate in the us-east-1 region. It seems like something changed on the AWS side so this likely has nothing to do with this project but figured this might help people who find things have suddenly broken.

Steps to reproduce the issue: 1. Build an image with buildah

# trimmed for brevity
buildah bud -v ~/podman_apt_cache:/var/cache/apt \
        --build-arg ... \
        --build-arg ... \
        --squash \
        -t ...
  1. Push to ECR
  2. Create service, task, etc
  3. Everything working, task starts, etc
  4. Delete and re-create the task + service (cloudformation), using previously created image
  5. Everything working, task starts, etc

As of yesterday 1. Delete and re-create the task + service (cloudformation), using previously created image 2. Service no longer starts, no logs from container

Describe the results you received:

ECS Fargate service reports error:

CannotPullContainerError: failed to find a descriptor for platform {linux/amd64}

Describe the results you expected: Expected the image to still work

Workaround Build the image with docker build. See also: https://forums.aws.amazon.com/thread.jspa?messageID=952613󨤥

Output of rpm -q buildah or apt list buildah:

$ apt list buildah
Listing... Done
buildah/unknown,now 1.15.1~1 amd64 [installed]
buildah/unknown 1.15.1~1 arm64
buildah/unknown 1.15.1~1 armhf
buildah/unknown 1.15.1~1 s390x

Output of buildah version:

$ buildah version
Version:         1.15.1
Go Version:      go1.14.2
Image Spec:      1.0.1-dev
Runtime Spec:    1.0.2-dev
CNI Spec:        0.4.0
libcni Version:  
image Version:   5.5.1
Git Commit:      
Built:           Thu Jan  1 10:00:00 1970
OS/Arch:         linux/amd64

Output of podman version if reporting a podman build issue:

$ podman version
Version:      2.0.4
API Version:  1
Go Version:   go1.14.2
Built:        Thu Jan  1 10:00:00 1970
OS/Arch:      linux/amd64

Output of cat /etc/*release:

$ cat /etc/*release
VERSION="20.04.1 LTS (Focal Fossa)"
PRETTY_NAME="Ubuntu 20.04.1 LTS"

Output of uname -a:

$ uname -a
Linux computer 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Output of cat /etc/containers/storage.conf:

$ cat /etc/containers/storage.conf
# This file is is the configuration file for all tools
# that use the containers/storage library.
# See man 5 containers-storage.conf for more information
# The "container storage" table contains all of the server options.

# Default Storage Driver
driver = ""

# Temporary storage location
runroot = "/var/run/containers/storage"

# Primary Read/Write location of container storage
graphroot = "/var/lib/containers/storage"

# Storage path for rootless users
# rootless_storage_path = "$HOME/.local/share/containers/storage"

# Storage options to be passed to underlying storage drivers

# AdditionalImageStores is used to pass paths to additional Read/Only image stores
# Must be comma separated list.
additionalimagestores = [

# Remap-UIDs/GIDs is the mapping from UIDs/GIDs as they should appear inside of
# a container, to the UIDs/GIDs as they should appear outside of the container,
# and the length of the range of UIDs/GIDs.  Additional mapped sets can be
# listed and will be heeded by libraries, but there are limits to the number of
# mappings which the kernel will allow when you later attempt to run a
# container.
# remap-uids = 0:1668442479:65536
# remap-gids = 0:1668442479:65536

# Remap-User/Group is a user name which can be used to look up one or more UID/GID
# ranges in the /etc/subuid or /etc/subgid file.  Mappings are set up starting
# with an in-container ID of 0 and then a host-level ID taken from the lowest
# range that matches the specified name, and using the length of that range.
# Additional ranges are then assigned, using the ranges which specify the
# lowest host-level IDs first, to the lowest not-yet-mapped in-container ID,
# until all of the entries have been used for maps.
# remap-user = "containers"
# remap-group = "containers"

# Root-auto-userns-user is a user name which can be used to look up one or more UID/GID
# ranges in the /etc/subuid and /etc/subgid file.  These ranges will be partioned
# to containers configured to create automatically a user namespace.  Containers
# configured to automatically create a user namespace can still overlap with containers
# having an explicit mapping set.
# This setting is ignored when running as rootless.
# root-auto-userns-user = "storage"
# Auto-userns-min-size is the minimum size for a user namespace created automatically.
# auto-userns-min-size=1024
# Auto-userns-max-size is the minimum size for a user namespace created automatically.
# auto-userns-max-size=65536

# ignore_chown_errors can be set to allow a non privileged user running with
# a single UID within a user namespace to run containers. The user can pull
# and use any image even those with multiple uids.  Note multiple UIDs will be
# squashed down to the default uid in the container.  These images will have no
# separation between the users in the container. Only supported for the overlay
# and vfs drivers.
#ignore_chown_errors = false

# Path to an helper program to use for mounting the file system instead of mounting it
# directly.
#mount_program = "/usr/bin/fuse-overlayfs"

# mountopt specifies comma separated list of extra mount options
mountopt = "nodev"

# Set to skip a PRIVATE bind mount on the storage home directory.
# skip_mount_home = "false"

# Size is used to set a maximum size of the container image.
# size = ""

# Storage Options for thinpool

# autoextend_percent determines the amount by which pool needs to be
# grown. This is specified in terms of % of pool size. So a value of 20 means
# that when threshold is hit, pool will be grown by 20% of existing
# pool size.
# autoextend_percent = "20"

# autoextend_threshold determines the pool extension threshold in terms
# of percentage of pool size. For example, if threshold is 60, that means when
# pool is 60% full, threshold has been hit.
# autoextend_threshold = "80"

# basesize specifies the size to use when creating the base device, which
# limits the size of images and containers.
# basesize = "10G"

# blocksize specifies a custom blocksize to use for the thin pool.
# blocksize="64k"

# directlvm_device specifies a custom block storage device to use for the
# thin pool. Required if you setup devicemapper.
# directlvm_device = ""

# directlvm_device_force wipes device even if device already has a filesystem.
# directlvm_device_force = "True"

# fs specifies the filesystem type to use for the base device.
# fs="xfs"

# log_level sets the log level of devicemapper.
# 0: LogLevelSuppress 0 (Default)
# 2: LogLevelFatal
# 3: LogLevelErr
# 4: LogLevelWarn
# 5: LogLevelNotice
# 6: LogLevelInfo
# 7: LogLevelDebug
# log_level = "7"

# min_free_space specifies the min free space percent in a thin pool require for
# new device creation to succeed. Valid values are from 0% - 99%.
# Value 0% disables
# min_free_space = "10%"

# mkfsarg specifies extra mkfs a


  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答


  • weixin_39945816 weixin_39945816 4月前

    Thanks for opening the issue, !

    Maybe there is an issue with OCI images on AWS. Could you try buildah-bud with --format docker? This instructs Buildah to build an image in the docker format rather than OCI.

    点赞 评论 复制链接分享
  • weixin_39942726 weixin_39942726 4月前

    confirming images built with --format docker work :beers:

    点赞 评论 复制链接分享
  • weixin_39615956 weixin_39615956 4月前

    good call. I seem to remember the AWS isn't happy with the OCI images.

    点赞 评论 复制链接分享
  • weixin_39615956 weixin_39615956 4月前

    I'm going to close this issue, please reopen if you think it needs further attention.

    点赞 评论 复制链接分享
  • weixin_39945816 weixin_39945816 4月前

    confirming images built with --format docker work

    Glad we found a work around :+1:

    点赞 评论 复制链接分享