Cannot commit and push container image from Kubernetes pods #827

nettoclaudio · 2022-02-19T20:06:06Z

Hello folks! 👋

I'm experiencing a strange behavior while committing a container (from Kubernetes pod) and pushing it to some container registry after. I always get the same error from the push command: content digest sha256:898c46f3b1a1f39827ed135f020c32e2038c87ae0690a8fe73d94e5df9e6a2d6: not found.

I'm filing this issue here but there's a chance the problem is on containerd side because I've already seen it working in an earlier version. I'm trying to find out which version it stopped to work.

I'm still investigating but no idea so far... suggestions are welcome.

Steps to reproduce:

Create an arbitrary Kubernetes pod (for simplicity w/ just one container).

$ kubectl run --image tsuru/go:latest my-app -- sleep Inf

Execute arbitrary commands to generate changes in the container image (to be committed):

$ kubectl exec my-app -- mkdir -p /tmp/foo/bar

Commit the container to a local image:

$ CONTAINER_ID=$(kubectl get pods my-app -o 'jsonpath={ .status.containerStatuses[0].containerID }' | sed -E 's|(.+)://||g')
$ nerdctl --namespace k8s.io commit ${CONTAINER_ID} registry.example.com/my-app:v1

Push to local registry (no credentials needed):

$ nerdctl --namespace k8s.io push registry.example.com/my-app:v1
FATA[0000] failed to create a tmp single-platform image "registry.example.com/my-app:v1-tmp-reduced-platform": content digest sha256:898c46f3b1a1f39827ed135f020c32e2038c87ae0690a8fe73d94e5df9e6a2d6: not found

Environment information:

nerdctl: 0.17.0
containerd: v1.4.12 7b11cfaabd73bb80907dd23182b9347b4245eb5d
OS: Buildroot 2021.02.4 (from minikube)
Kernel: 4.19.202
Kubernetes version: v1.20.6
kubectl version: v1.20.6
Minikube: v1.25.1

The text was updated successfully, but these errors were encountered:

junnplus · 2022-03-20T09:29:45Z

I can't reproduce this problem on containerd with latest and 1.5.10 version.

jun@lima-k8s-test:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.6", GitCommit:"8a62859e515889f07e3e3be6a1080413f17cf2c3", GitTreeState:"clean", BuildDate:"2021-04-15T03:28:42Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.6", GitCommit:"8a62859e515889f07e3e3be6a1080413f17cf2c3", GitTreeState:"clean", BuildDate:"2021-04-15T03:19:55Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
jun@lima-k8s-test:~$ containerd -v
containerd containerd.io 1.5.10 2a1d4dbdb2a1030dc5b01e96fb110a9d9f150ecc

In addition, I can't start the corresponding containerd version through minikube.

PS: containerd v1.4.x reached EOL.

junnplus · 2022-06-29T09:14:14Z

I closed it because containerd v1.4.x reached EOL.

Feel free to open it up if you have any other questions.

Nirmit1995 · 2023-05-31T14:37:56Z

I am also getting the same error for large images (mine was 7GB, small images were easily pushed)

FATA[0000] failed to create a tmp single-platform image "registry.example.com/my-app:0086bf16-21cb-477b-952c-13780780f597-tmp-reduced-platform": content digest sha256:5bed26d33875e6da1d9ff9a1054c5fef3bbeb22ee979e14b72acf72528de007b: not found

I have the following config-
[ec2-user@ip]$ sudo /usr/local/bin/nerdctl version
WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH
Client:
Version: v1.4.0
OS/Arch: linux/amd64
Git commit: 7e8114a
buildctl:
Version:

Server:
containerd:
Version: 1.6.19
GitCommit: 1e1ea6e986c6c86565bc33d52e34b81b3e2bc71f
runc:
Version: 1.1.4
GitCommit: 5fd4c4d144137e991c4acebb2146ab1483a97925

Please help in resolving this.

HFfleming · 2023-06-25T02:34:56Z

could you please reopen the issue, @junnplus thanks.
I meet the same problem : I commit the image from a running container, then i need push the new image to my repo.
when i use nerdctl -n k8s.io push xxx ,an error occurs:
FATA[0000] failed to create a tmp single-platform image "xxx.com/hjmtest/nginx:hjm-tmp-reduced-platform": content digest sha256:550fe1bea624a5c62551cf09f3aa10886eed133794844af1dfb775118309387e: not found

here is my env info:
nerdctl -v nerdctl version 1.4.0
containerd -v containerd github.com/containerd/containerd v1.6.14-42-g21f32b2c3 21f32b2c394bc1ccfbf1744876a0fcdd4ef2390d

HFfleming · 2023-06-25T02:50:23Z

could you please open this issue, @junnplus thanks. I meet the same problem : I commit the image from a running container, then i need push the new image to my repo. when i use nerdctl -n k8s.io push xxx ,an error occurs: FATA[0000] failed to create a tmp single-platform image "xxx.com/hjmtest/nginx:hjm-tmp-reduced-platform": content digest sha256:550fe1bea624a5c62551cf09f3aa10886eed133794844af1dfb775118309387e: not found

here is my env info: nerdctl -v nerdctl version 1.4.0 containerd -v containerd github.com/containerd/containerd v1.6.14-42-g21f32b2c3 21f32b2c394bc1ccfbf1744876a0fcdd4ef2390d

In addition:
if i pull images from others, not commit a new image, nerdctl push xxx can work.

ggerogery · 2023-07-08T19:55:33Z

I got the same issue but with finch.
Solved with --platform arg:
finch push xxx.dkr.ecr.us-east-1.amazonaws.com/infra/calico/apiserver:v3.25.1 --platform linux/amd64

baozaolaoba-top · 2023-09-09T16:45:46Z

In addition:

nerdctl version 1.5.0
containerd -v
containerd github.com/containerd/containerd v1.7.1 1677a17964311325ed1c31e2c0a3589ce6d5c30d

harbor server with port: hub.local:5443

Zheaoli · 2023-09-18T14:10:07Z

WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH 
Client:
 Version:       v1.5.0
 OS/Arch:       linux/amd64
 Git commit:    b33a58f288bc42351404a016e694190b897cd252
 buildctl:
  Version:

Server:
 containerd:
  Version:      1.7.1+azure-1
  GitCommit:    1677a17964311325ed1c31e2c0a3589ce6d5c30d
 runc:
  Version:      1.1.7
  GitCommit:    860f061b76bb4fc671f0f9e900f7d80ff93d4eb7

could not produce this bug. would you guys mind to give me reproduce step with more detail? like what's registry you use

JCereal · 2023-11-08T06:09:51Z

Recently, my GKE cluster's worker node upgraded to v1.27.3-gke.100 which also upgraded containerd from 1.6.18 to 1.7.0. After the upgrade, I encountered the exact same issue.

Client:
 Version:	v1.7.0
 OS/Arch:	linux/amd64
 Git commit:	e674fe7ba6e49f12e88cd9c6c442e7ea5232502c
 buildctl:
  Version:	v0.12.3
  GitCommit:	438f47256f0decd64cc96084e22d3357da494c27

Server:
 containerd:
  Version:	1.7.0
  GitCommit:	1fbd70374134b891f97ce19c70b6e50c7b9f4e0d
 runc:
  Version:	1.1.10
  GitCommit:	v1.1.10-0-g18a0cb0f

Reproduce

The commit command: nerdctl -n k8s.io commit bbe68406a258 some.registry.com/my-app:0.1

The push command like: nerdctl -n k8s.io push some.registry.com/my-app:0.1

Output: FATA[0000] failed to create a tmp single-platform image "some.registry.com/my-app:0.1-tmp-reduced-platform": content digest sha256:c95ff01263cbbb536e71f8ae823d3e63f15f7a0f1ba9ecb7b3126a63654d2b23: not found.

Work around

Add --all-platforms option.

If I run the push command like: nerdctl -n k8s.io push --all-platforms some.registry.com/my-app:0.1, the image can be pushed if the registry is valid (btw I pushed to JFrog).

The option is added to avoid converter.Convert. Related code:

nerdctl/pkg/cmd/image/push.go

Lines 98 to 111 in ce2f63d

    
           if !options.AllPlatforms { 
        
           	pushRef = ref + "-tmp-reduced-platform" 
        
           	// Push fails with "400 Bad Request" when the manifest is multi-platform but we do not locally have multi-platform blobs. 
        
           	// So we create a tmp reduced-platform image to avoid the error. 
        
           	platImg, err := converter.Convert(ctx, client, pushRef, ref, converter.WithPlatform(platMC)) 
        
           	if err != nil { 
        
           		if len(options.Platforms) == 0 { 
        
           			return fmt.Errorf("failed to create a tmp single-platform image %q: %w", pushRef, err) 
        
           		} 
        
           		return fmt.Errorf("failed to create a tmp reduced-platform image %q (platform=%v): %w", pushRef, options.Platforms, err) 
        
           	} 
        
           	defer client.ImageService().Delete(ctx, platImg.Name, images.SynchronousDelete()) 
        
           	log.G(ctx).Infof("pushing as a reduced-platform image (%s, %s)", platImg.Target.MediaType, platImg.Target.Digest) 
        
           }

Other info

The issue is not registry related. I tried different registries, the same error is thrown, even with random invalid registry.

The container I am committing from is built on an Ubuntu machine with docker build . command, without specifying the platform as linux/amd64.

When it used to work with containerd 1.6.18, I can see the log level=info msg="pushing as a reduced-platform image.... The convert should be good then.

beyou923 · 2023-12-07T10:15:34Z

I started a container using the nydus format and then packaged the container into an image. However, I encountered the same problem when I tried to push this image.

Steps to reproduce:

Create a container with nydus image

nerdctl --snapshotter nydus run --cap-add=CAP_SYS_ADMIN  --net host -it  registry-test.xx.info/library/nydus-image:old

Commit the container to a local image:

nerdctl  commit ${CONTAINER_ID} registry-test.xx.info/library/nydus-image:new

Push to registry (no credentials needed):

nerdctl push registry-test.xx.info/library/nydus-image:new
FATA[0000] failed to create a tmp single-platform image " registry-test.xx.info/library/nydus-image:new-tmp-reduced-platform": content digest sha256:cfc7393224358fb100dabf40f7d59c2578c0a6a47781b1a6b56406922aeb6e95: not found

env info:

Kernel: 4.9.144
nerdctl version 1.6.2
containerd: v1.5.9
nydusd version: v2.2.3
containerd-nydus-grpc version: v0.13.3

Does the container launched by on-demand loading of images support commit and push operations?

iholo · 2024-02-06T02:51:20Z

I have the same problem on Azure

env info:
kubernetes: v1.27.7
Kernel: 5.15.0-1053-azure
nerdctl version 1.7.3
containerd: 1.7.1+azure-1

michaelmalice · 2024-06-20T01:32:12Z

Hi I'm having the same issue. Is there a specific version of containerd that I can use that doesn't have this problem?

hj1801 · 2024-06-27T08:52:28Z

I am encountering the same issue.
It seems to occur from kubernetes 1.27 version, and it remains unresolved even when using the latest version of nerdctl (1.7.6). As someone else pointed out, the --all-platforms or --platform flag does not work while pushing.
Looking at the issue, it seems that it starts from failing to save a committed image.

This has been an ongoing issue since the past and I am wondering if there have been any follow-ups on this matter.

zgfh · 2024-07-26T11:39:25Z

this work for me : nerdctl tag with a new image neme ,then push again

lingdie · 2024-08-01T07:35:50Z

By default, commit image will not be unpacked to snapshots.

ctr --namespace=k8s.io i check
REF                                                                     TYPE                                                 DIGEST                                                                  STATUS           SIZE                UNPACKED
docker.io/lingdie/busybox:commit                                        application/vnd.docker.distribution.manifest.v2+json sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72 complete (4/4)   28.3 MiB/28.3 MiB   false

Unpacking the image may solve the problem:

ctr --namespace=k8s.io snapshots unpack sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72
unpacking sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72 (application/vnd.docker.distribution.manifest.v2+json)...done


nerdctl --namespace k8s.io image convert lingdie/busybox:commit lingdie/busybox:tmp
sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72

nerdctl --namespace k8s.io image push lingdie/busybox:tmp
INFO[0000] pushing as a reduced-platform image (application/vnd.docker.distribution.manifest.v2+json, sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72)
manifest-sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72: done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:55fefd844bcb12134766ab042567efccb311ad9f051e68497c6a207dbdbe7afc:   done           |++++++++++++++++++++++++++++++++++++++|
elapsed: 5.0 s                                                                    total:  2.5 Ki (509.0 B/s)

lingdie · 2024-08-01T08:04:05Z

this pr may fix this:

#3268

apostasie · 2024-08-12T04:55:50Z

@lingdie testing on main from today, the issue is still there (as described by OP).

Wondering what we are missing here...

lingdie · 2024-08-13T08:36:12Z

Here is my testing process. Could you please provide your testing?

apostasie · 2024-08-13T15:31:10Z

@lingdie

kind version 0.23.0

nerdctl latest main

ubuntu 24.04 (in lima on a mac M1 with Sonoma 14.5)

kind.yaml:

# https://pkg.go.dev/sigs.k8s.io/kind/pkg/apis/config/v1alpha4#Cluster
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
    extraMounts:
      - hostPath: _output/nerdctl
        containerPath: /usr/local/bin/nerdctl
      - hostPath: /tmp/go
        containerPath: /usr/local/go
      - hostPath: .
        containerPath: /nerdctl-source

Create the cluster:

make binaries

KIND_EXPERIMENTAL_PROVIDER=nerdctl kind create cluster --config=./kind.yaml

nerdctl exec -ti kind-control-plane bash

Inside the control plane from above:

kubectl run --image debian my-app -- sleep Inf
kubectl exec my-app -- mkdir -p /tmp/foo/bar
CONTAINER_ID=$(kubectl get pods my-app -o "jsonpath={ .status.containerStatuses[0].containerID }" | sed -E "s|(.+)://||g")

nerdctl --namespace k8s.io commit ${CONTAINER_ID} registry.example.com/my-app:v1
nerdctl --namespace k8s.io push registry.example.com/my-app:v1

More info:

root@kind-control-plane:/# nerdctl info
Client:
 Namespace:	default
 Debug Mode:	false

Server:
 Server Version: v1.7.15
 Storage Driver: overlayfs
 Logging Driver: json-file
  Cgroup Driver:  : systemd
  Cgroup Version: : 2
 Plugins:
  Log:     fluentd journald json-file syslog
  Storage: native overlayfs fuse-overlayfs
 Security Options:
  apparmor
  seccomp
   Profile:	builtin
  cgroupns
 Kernel Version:   6.8.0-31-generic
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType:           linux
 Architecture:     aarch64
 CPUs:             4
 Total Memory:     3.814GiB
 Name:             kind-control-plane
 ID:               c74d79a4-7d13-4eca-ae50-6e2e95ae5043

WARNING: No swap limit support

@lingdie let me know if I am missing something here, or if you need anything else.

Also, when we get #3296 in we will be able to test for Kube on the CI (in the same conditions, using Kind).

apostasie · 2024-08-14T05:13:15Z

@lingdie there is clearly something wrong going on with this.

This issue keeps cropping up on a variety of operations - save, commit, with or without kube - #3179

I believe these have all the same root issue, but I cannot pinpoint it...

ouyangningdong · 2024-08-20T06:49:17Z

Regarding the issue of saving snapshots into tar files, has it been resolved? Do I use the latest version 2.0.0-rc1, but it still prompts that some levels of sha256 cannot be found. Is it lost due to garbage collection?

apostasie · 2024-08-21T03:38:39Z

@ouyangningdong if your issue is the same that is being discussed here, it is not resolved - and the ticket is still open.

If your issue is different, I suggest you open a new ticket.

Also, it does not seem like a garbage collection problem.

apostasie · 2024-08-21T21:29:03Z

@lingdie I did add the scenario as a test (https://github.com/containerd/nerdctl/blob/main/cmd/nerdctl/container_commit_linux_test.go#L28) - right now, the test expectation is to fail (until we fix the problem).

Interestingly, the test failed once on an unrelated PR:
https://github.com/containerd/nerdctl/actions/runs/10497512059/job/29080522608

... meaning the problem might be racy?

lingdie · 2024-08-23T06:15:24Z

The only thing I can think of is that containerd might have garbage collected some essential layers...

Signed-off-by: apostasie <spam_blackhole@farcloser.world>

Disable flaky #827 test

lingdie · 2024-09-09T03:51:47Z

I believe I have found the source of the problem. Below is my reproduction process:

Start the pod

kubectl run busybox --image busybox -- sleep 12000

Check the original image, find it's in an incomplete state

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true

Commit the container

containerID=$(kubectl get pods -o go-template='{{range .items}}{{range .status.containerStatuses}}{{if eq .name "busybox"}}{{.containerID}}{{"\n"}}{{end}}{{end}}{{end}}' | grep -oP '(?<=containerd://)\w+')

nerdctl commit $containerID docker.io/lingdie/busybox:dev

Check the committed image, it's also in an incomplete state

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/lingdie/busybox:dev                                                                     application/vnd.docker.distribution.manifest.v2+json      sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e incomplete (2/3) 791.0 B/1.8 MiB     true

Try to push the image using nerdctl, which of course fails

nerdctl push docker.io/lingdie/busybox:dev
FATA[0000] failed to create a tmp single-platform image "docker.io/lingdie/busybox:dev-tmp-reduced-platform": content digest sha256:75e8ca8f509fb8f7ee74430edbdc5b78fd863a4f08e06c53828e9a996a79f642: not found

Use ctr to pull the image again

ctr --namespace k8s.io image pull docker.io/library/busybox:latest
docker.io/library/busybox:latest:                                                 resolved       |++++++++++++++++++++++++++++++++++++++|
index-sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41:    exists         |++++++++++++++++++++++++++++++++++++++|
manifest-sha256:e7e097403ca9266ab43ca83b3b55c272c248cf46489a40bcc4864bd7dd945f18: exists         |++++++++++++++++++++++++++++++++++++++|
layer-sha256:75e8ca8f509fb8f7ee74430edbdc5b78fd863a4f08e06c53828e9a996a79f642:    done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:fd633c23ab56c682e69aacf7fea8d0eaa8d18bd72c4b1c6d82eb5eaace658f1a:   exists         |++++++++++++++++++++++++++++++++++++++|
elapsed: 8.0 s                                                                    total:  1.0 Mi (128.0 KiB/s)
unpacking linux/arm64/v8 sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41...
done: 9.078793ms

Check the image

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 complete (2/2)   1.8 MiB/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 complete (2/2)   1.8 MiB/1.8 MiB     true
docker.io/lingdie/busybox:dev                                                                     application/vnd.docker.distribution.manifest.v2+json      sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e complete (3/3)   1.8 MiB/1.8 MiB     true

Push the image using nerdctl, success...

nerdctl push docker.io/lingdie/busybox:dev
INFO[0000] pushing as a reduced-platform image (application/vnd.docker.distribution.manifest.v2+json, sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e)
manifest-sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e: done           |++++++++++++++++++++++++++++++++++++++|
layer-sha256:eb86545fdbaa77abb944627619e66fb8c1853b427fc930493c561988674054be:    done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:f78592bf867943251d217918b2299bbd7191970ae83dc52a8afc5e7ad98bf71d:   done

lingdie · 2024-09-09T03:55:41Z

see: containerd/containerd#8973

AkihiroSuda added the bug Something isn't working label Feb 20, 2022

junnplus added the status/needs-more-information Needs more information from OP label Mar 20, 2022

junnplus closed this as completed Jun 29, 2022

Zheaoli reopened this Sep 18, 2023

Zheaoli mentioned this issue Sep 18, 2023

nerdctl push command not working when using minikube with containerd (invalid checksum digest format) #2506

Closed

VannTen mentioned this issue Dec 1, 2023

Workaround nerctl not finding layer kubernetes-sigs/kubespray#10683

Closed

piccaSun mentioned this issue Mar 28, 2024

fix(ai): Containerd运行时下大镜像推送失败 PKUHPC/OpenSCOW#1181

Merged

apostasie mentioned this issue Jul 30, 2024

nerctl commit image couldn‘t push #3248

Closed

This comment was marked as outdated.

Sign in to view

lingdie mentioned this issue Aug 1, 2024

fix: add unpack logic after container commit to images. #3268

Merged

This was referenced Aug 1, 2024

[WIP] Login rework #3249

Closed

Add a Kube testing environment? #3282

Closed

apostasie mentioned this issue Aug 12, 2024

Kube on the CI #3296

Merged

apostasie mentioned this issue Aug 12, 2024

In the EKS cluster, I encountered an error using NERDCTL to save containerd, not found #3298

Open

This comment was marked as outdated.

Sign in to view

apostasie added a commit to apostasie/nerdctl that referenced this issue Aug 28, 2024

Disable flaky containerd#827 test

b12cdf5

Signed-off-by: apostasie <spam_blackhole@farcloser.world>

apostasie added a commit to apostasie/nerdctl that referenced this issue Aug 28, 2024

Disable flaky containerd#827 test

68be0ce

Signed-off-by: apostasie <spam_blackhole@farcloser.world>

AkihiroSuda added a commit that referenced this issue Aug 28, 2024

Merge pull request #3374 from apostasie/chore-kube-grrrr

4ab2866

Disable flaky #827 test

apostasie mentioned this issue Sep 5, 2024

Error nerdctl commit, "failed to create a tmp single-platform image..., content digest ... not found" #3415

Closed

This was referenced Sep 10, 2024

Build fail with "parent snapshot does not exist" #3420

Closed

Issues related to missing layer (likely caused by https://github.com/containerd/containerd/issues/8973 ) #3425

Closed

apostasie mentioned this issue Sep 24, 2024

Ensure all layers are here when tagging, committing, saving, or converting #3435

Merged

AkihiroSuda closed this as completed in #3435 Oct 2, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot commit and push container image from Kubernetes pods #827

Cannot commit and push container image from Kubernetes pods #827

nettoclaudio commented Feb 19, 2022 •

edited

Loading

junnplus commented Mar 20, 2022 •

edited

Loading

junnplus commented Jun 29, 2022

Nirmit1995 commented May 31, 2023 •

edited

Loading

HFfleming commented Jun 25, 2023 •

edited

Loading

HFfleming commented Jun 25, 2023 •

edited

Loading

ggerogery commented Jul 8, 2023

baozaolaoba-top commented Sep 9, 2023 •

edited

Loading

Zheaoli commented Sep 18, 2023

JCereal commented Nov 8, 2023 •

edited

Loading

beyou923 commented Dec 7, 2023 •

edited

Loading

iholo commented Feb 6, 2024

michaelmalice commented Jun 20, 2024

hj1801 commented Jun 27, 2024

zgfh commented Jul 26, 2024 •

edited

Loading

This comment was marked as outdated.

lingdie commented Aug 1, 2024 •

edited

Loading

lingdie commented Aug 1, 2024

apostasie commented Aug 12, 2024

lingdie commented Aug 13, 2024

apostasie commented Aug 13, 2024 •

edited

Loading

This comment was marked as outdated.

apostasie commented Aug 14, 2024

ouyangningdong commented Aug 20, 2024 •

edited

Loading

apostasie commented Aug 21, 2024

apostasie commented Aug 21, 2024

lingdie commented Aug 23, 2024

lingdie commented Sep 9, 2024

lingdie commented Sep 9, 2024

Cannot commit and push container image from Kubernetes pods #827

Cannot commit and push container image from Kubernetes pods #827

Comments

nettoclaudio commented Feb 19, 2022 • edited Loading

Steps to reproduce:

Environment information:

junnplus commented Mar 20, 2022 • edited Loading

junnplus commented Jun 29, 2022

Nirmit1995 commented May 31, 2023 • edited Loading

HFfleming commented Jun 25, 2023 • edited Loading

HFfleming commented Jun 25, 2023 • edited Loading

ggerogery commented Jul 8, 2023

baozaolaoba-top commented Sep 9, 2023 • edited Loading

Zheaoli commented Sep 18, 2023

JCereal commented Nov 8, 2023 • edited Loading

beyou923 commented Dec 7, 2023 • edited Loading

Steps to reproduce:

env info:

iholo commented Feb 6, 2024

michaelmalice commented Jun 20, 2024

hj1801 commented Jun 27, 2024

zgfh commented Jul 26, 2024 • edited Loading

This comment was marked as outdated.

lingdie commented Aug 1, 2024 • edited Loading

lingdie commented Aug 1, 2024

apostasie commented Aug 12, 2024

lingdie commented Aug 13, 2024

apostasie commented Aug 13, 2024 • edited Loading

This comment was marked as outdated.

apostasie commented Aug 14, 2024

ouyangningdong commented Aug 20, 2024 • edited Loading

apostasie commented Aug 21, 2024

apostasie commented Aug 21, 2024

lingdie commented Aug 23, 2024

lingdie commented Sep 9, 2024

lingdie commented Sep 9, 2024

nettoclaudio commented Feb 19, 2022 •

edited

Loading

junnplus commented Mar 20, 2022 •

edited

Loading

Nirmit1995 commented May 31, 2023 •

edited

Loading

HFfleming commented Jun 25, 2023 •

edited

Loading

HFfleming commented Jun 25, 2023 •

edited

Loading

baozaolaoba-top commented Sep 9, 2023 •

edited

Loading

JCereal commented Nov 8, 2023 •

edited

Loading

beyou923 commented Dec 7, 2023 •

edited

Loading

zgfh commented Jul 26, 2024 •

edited

Loading

lingdie commented Aug 1, 2024 •

edited

Loading

apostasie commented Aug 13, 2024 •

edited

Loading

ouyangningdong commented Aug 20, 2024 •

edited

Loading