Skip to content

Pulling busybox on arm fails #3387

@rkojedzinszky

Description

@rkojedzinszky

Description

Installed containerd as CRI for k8s on arm, and actually containerd cannot download busybox image.

Steps to reproduce the issue:

  1. Setup containerd / k8s as described in kubeadm setup guide on debian/ubuntu
  2. Create a pod with image: busybox

Describe the results you received:

In the logs, I see:

Jul 02 18:49:06 k8s-node09 containerd[1138]: time="2019-07-02T18:49:06.987317311Z" level=info msg="PullImage "busybox:latest""
Jul 02 18:49:07 k8s-node09 containerd[1138]: time="2019-07-02T18:49:07.734548526Z" level=info msg="Events for "docker.io/library/busybox:latest" is in backoff, enqueue event &ImageUpdate{Name:docker.io/library/busybox:latest,Labels:map[string]string{},}"
Jul 02 18:49:07 k8s-node09 containerd[1138]: time="2019-07-02T18:49:07.736910269Z" level=error msg="PullImage "busybox:latest" failed" error="failed to pull and unpack image "docker.io/library/busybox:latest": failed to unpack image on snapshotter overlayfs: content digest sha256:76535ae6ed1a2a69f5c4fdf6d0a5b17da86f797cb7ac15c06dd74fe44e454db2: not found"

Describe the results you expected:

I expect that a simple busybox image can be pulled, a simple pod can be started up.

Output of containerd --version:

# containerd --version
containerd containerd.io 1.2.6 894b81a4b802e4eb2a91d1ce216b8817763c29fb

Any other relevant information:

The following also fails:

# ctr i pull docker.io/library/busybox:latest

But, when ctr binary compiled from master, it can download the image. Strange is that, containerd binary from that source still fails downloading busybox image.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions