containerd / containerd/accelerated-container-image

nerdctl running image and crictl interfere with each other

Open
#262 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
470
Forks
87
Avg merge
2d 21h
Merged PRs (30d)
5

Description

### What happened in your environment?

FIrst run `nerdctl run --snapshotter overlaybd --network none -it pytorch2`
Then submit a pod using `pytorch2` image, the pod will create error

### What did you expect to happen?

It is expected that an image can be run multiple times without affecting each other.

### How can we reproduce it?

FIrst run `nerdctl run --snapshotter overlaybd --network none -it pytorch2`
Then submit a pod using `pytorch2` image, the pod will create error

### What is the version of your Accelerated Container Image?

1.0.2

### What is your OS environment?

Ubuntu 22.04

### Are you willing to submit PRs to fix it?

- [ ] Yes, I am willing to fix it.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with `nerdctl run --snapshotter overlaybd --network none -it pytorch2`, then submit a pod using the same image and compare the resulting error. Trace the interaction between the nerdctl and crictl entry points and the overlaybd snapshotter; done means the image can be run through both paths without either affecting the other.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.