Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"failed to release stub drive for container" error for stopping container #370

Closed
haikuoliu opened this issue Dec 18, 2019 · 3 comments
Closed

"failed to release stub drive for container" error for stopping container #370

haikuoliu opened this issue Dec 18, 2019 · 3 comments
Assignees
@kzys

Comments

@haikuoliu
Copy link

Full error:

* failed to release stub drive for container: 3b95ef1f-202c-414b-8d9d-f1260790e683: failed to unmount drive: rpc error: code = NotFound desc = method UnmountDrive

I am using latest firecracker containerd, and I launched a VM with jailer, the VM was running, then I launched a container that sleeps forever, when I tried to kill the container, I got error above. I was using AmazonLinux 2 rootfs (writable) and it has latest fc-containerd agent installed.

Is that something to do with firecracker-containerd or the rootfs itself?
@kzys kzys self-assigned this Jan 6, 2020
@kzys
Copy link
Contributor

kzys commented Jan 6, 2020

Can you rebuild your rootfs image from the latest source?

You got code = NotFound desc = method UnmountDrive and the UnmountDrive method is relatively new (added by #339). Your in-VM agent might not have the method.

@haikuoliu
Copy link
Author

I just rebuilt the rootfs with the latest VM agent (b95b5093ea5e44c42594aa922e593e02c3aa2438), but still got same error. When my container exits itself (instead of being killed), it works normally, I think the stub drive should be released no matter of the container is killed or not right?

@haikuoliu
Copy link
Author

Sorry my latest agent wasn't copied over to the al2 rootfs due to a bug in my build script, my bad, close this issue.

kzys added a commit to kzys/firecracker-containerd that referenced this issue Jan 9, 2020
@kzys
Add -version flag to the in-VM agent
2f4a1bf 
Investigating issues like firecracker-microvm#370 will be easier if the agent can report
the version.
@kzys kzys mentioned this issue Jan 9, 2020
Merged
kzys added a commit to kzys/firecracker-containerd that referenced this issue Jan 9, 2020
@kzys
Add -version flag to the in-VM agent
5606c60 
Investigating issues like firecracker-microvm#370 will be easier if the agent can report
the version.

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
kzys added a commit to kzys/firecracker-containerd that referenced this issue Jan 9, 2020
@kzys
Add -version flag to the in-VM agent
12a752d 
Investigating issues like firecracker-microvm#370 will be easier if the agent can report
the version.

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
kzys added a commit to kzys/firecracker-containerd that referenced this issue Jan 9, 2020
@kzys
Add -version flag to the in-VM agent
80f87c9 
Investigating issues like firecracker-microvm#370 will be easier if the agent can report
the version.

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
ustiugov pushed a commit to vhive-serverless/firecracker-containerd that referenced this issue Jan 30, 2020
@kzys @ustiugov
Add -version flag to the in-VM agent
5843519 
Investigating issues like firecracker-microvm#370 will be easier if the agent can report
the version.

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
fangn2 pushed a commit to fangn2/firecracker-containerd that referenced this issue Mar 23, 2023
@kzys
Merge pull request firecracker-microvm#370 from kzys/go115
195bc24 
Upgrade Go from 1.13 to 1.15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kzys kzys

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kzys @haikuoliu