-
Notifications
You must be signed in to change notification settings - Fork 182
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.
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
Failed to extract layer from example remote snapshotter #709
Comments
From the firecracker-containerd output, it looks like you're having auth issues:
For GHCR, the docker username is your GitHub username and docker password is a personal access token. If you haven't created an access token, you can follow https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry. If you have, can you verify that you're passing those correctly? |
Hi Kern! Ah, I was using my actual password for it. However, after inserting my credentials accordingly, I am now getting:
Is this part of the actual image or could this be related to a setup issue? |
Do you have the firecracker-containerd logs from that most recent failure? |
Sure. I have added it as a file EDIT: |
Hi @Kern--. Apologies for the disturbance, but I wanted to ask if there is any update you may give me on this issue. Any pointers as to what could be wrong would be useful. I did take my time to look into the IOProxy class as it seems to be the one delegated to perform the IO operations that seem to file, though I am not sure where the file |
Current vHive CloudLab profile uses Ubuntu 20.04 image, which does not have the skopeo package which is needed to pull image for local registry tests — temporarily disable these tests until firecracker-microvm#709 is resolved. Closes firecracker-microvm#703 Signed-off-by: Georgiy Lebedev <[email protected]>
Hi! I'm David and I am interested in making use of the
firecracker-containerd
in the context of remote snapshots using thestargz
snapshotter.I have followed the setup provided for running containers using remote snapshots as described below, but came across an issue when creating the task for the stargz based image. Further details are provided below and I am most thankful for your time!
Setup details
System
$ uname -a Linux node-1.dbuzatu-138770.faas-sched-pg0.cloudlab.umass.edu 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Installation
Installed
main
version offirecracker-containerd
by following the steps from quickstart.Using firecracker-containerd to start a Docker based container using the following script works as expected:
Issue (UPDATED)
After following the remote snapshotter setup guide, running the command:
results in the following output:
Creating VM Setting docker credential metadata Pulling the image Creating a container Creating a task failed to create shim task: failed to create task: rpc error: code = Unknown desc = OCI runtime create failed: unable to retrieve OCI runtime error (open /container/remoteSnapshotterDemo/log.json: no such file or directory): runc did not terminate successfully: exit status 2: unknown
Firecracker-containerd logs gist:
The text was updated successfully, but these errors were encountered: