Remote snapshotter example fails on docker image with failed to mount <...>: no such file or directory: unknown error
#761
Comments
CuriousGeorgiy
changed the title
ttrpc: refusing connection after handshake errorfailed to mount <...>: no such file or directory: unknown error
|
I fixed the issue with pulling images from The code in the example was setting the key as dockerHost := refSpec.Hostname()
// Adjust host key for Docker Hub
if dockerHost == "docker.io" {
dockerHost = "https://index.docker.io/v1/"
}With this change, the custom image was successfully pulled, and the container started as expected. Next, I’ll address the issue with the local registry. |
|
I fixed the issue when pulling from a local registry. First, we shouldn't use Next, I encountered an issue related to the local registry using HTTP. After reviewing the stargz documentation, I discovered that we can configure insecure connections for specific registries. To resolve this, I updated the configuration file located at Finally, I used Docker to pull your image, tagged it, and pushed it to my own repository. However, I encountered issues when pulling the image using the snapshotter, similar to what is described here. As suggested here, I switched to using |
I followed the remote snapshotter getting starting guide for the instance setup (I am using the latest firecracker version) and the instructions from the remote snapshotter example README, but when I launch the example with my public image, it fails with the following error:
The following errors appear in the firecracker-containerd logs:
docker loginon the same host with the same credentials succeeds.If I try to pull the same image from the GHCR, providing my GitHub PAT as the password, the example also fails:
If I try to pull the same image from a local docker registry, which doesn't require any authentication, I get the same error as in the first case:
The following errors appear in the firecracker-containerd logs:
Again, I can pull from the local registry using docker just fine.
The text was updated successfully, but these errors were encountered: