-
Notifications
You must be signed in to change notification settings - Fork 213
You could find them in: https://github.com/dragonflyoss/image-service/tree/master/docs
You could using nerdctl to sync nydus images with --unpack false
nerdctl pull --unpack false tomcat:latestnydusv6
nerdctl tag tomcat:latestnydusv6 ghcr.io/username/tomcat:latestnydusv6
nerdctl push --allow-nondistributable-artifacts ghcr.io/username/tomcat:latestnydusv6
Try nydus >= v2.1.4
, the version fixed the nydusd error when running the images created by nydusify/buildkit/acceld
using nydus-image >= 2.2
, strongly recommend all users to upgrade.
Q: Can't start nydus pod in K8s. Error: failed to get reader from content store: content digest sha256:*** not found
You could try to set discard_unpapcked_layers = false
in /etc/containerd/config.toml
[plugins."io.containerd.grpc.v1.cri".containerd]
discard_unpacked_layers = false
Or please refer to the following documents to deploy pods in k8s: https://github.com/containerd/nydus-snapshotter/blob/main/docs/run_nydus_in_kubernetes.md
Q: Can't start nydus image. Error: failed to get stream processor for application/vnd.oci.image.layer.nydus.blob.v1: no processor for media-type: unknown
Nydus-snapshotter is not selected by containerd, causing the nydus image to fail to be parsed.
You could try to configure [proxy_plugins]
in /etc/containerd/config.toml
[proxy_plugins]
[proxy_plugins.nydus]
type = "snapshot"
address = "/run/containerd-nydus/containerd-nydus-grpc.sock"
If you wish to switch containerd's default snapshotter to nydus, you can also configure [plugins."io.containerd.grpc.v1.cri".containerd]
in /etc/containerd/config.toml
[plugins."io.containerd.grpc.v1.cri".containerd]
snapshotter = "nydus"
disable_snapshot_annotations = false