# Air-gap installations and nerdctl

**URL:** <https://forums.suse.com/t/air-gap-installations-and-nerdctl/37567>\
**Category:** k3s, k3OS, and k3d\
**Created:** [April 11, 2022, 1:37pm UTC](https://forums.suse.com/t/air-gap-installations-and-nerdctl/37567 "2022-04-11T13:37:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eldan](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Eldan](https://forums.suse.com/u/Eldan)\
**Post date:** [April 11, 2022, 1:37pm UTC](https://forums.suse.com/t/air-gap-installations-and-nerdctl/37567/1 "2022-04-11T13:37:08Z")

</div>

I was successfully using the air-gap ‘[https://rancher.com/docs/k3s/latest/en/installation/airgap/#prepare-the-images-directory-and-k3s-binary](https://rancher.com/docs/k3s/latest/en/installation/airgap/#prepare-the-images-directory-and-k3s-binary)Manually deploy images method’ for my application images.

However, I moved from docker-desktop to rancher-desktop (uses nerdctl) but now the ‘nerdctl save’ command creates a tar file in a format that k3s cannot read (the tar has the ‘blobs’ folder). Previously, with docker, the tar was properly readable (the tar has the ‘repositories’ and ‘manifest.json’).

How can I instruct k3s to use the tar images in its ‘\var\lib\rancher\k3s\agent\images’ folder to read the ‘blobs’ format?  
Or the other way around , to have ‘nerdctl save’ create a tar with the ‘repositories’ and ‘manifest.json’ format?

Thanks

---

<div class="post-metadata">

**Author:** ![Stephen\_Goveia](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stephen_goveia/32/8378_2.png) [@Stephen\_Goveia](https://forums.suse.com/u/Stephen_Goveia)\
**Post date:** [November 22, 2022, 2:36pm UTC](https://forums.suse.com/t/air-gap-installations-and-nerdctl/37567/2 "2022-11-22T14:36:34Z")

</div>

You can use skopeo to do this:

```auto
skopeo copy docker://docker.io/library/registry:2 docker-archive:./registry.tar:library/registry:2

```

the registry.tar should be in the correct format for k3s.

ref:  
[https://itnext.io/running-k3s-workload-in-a-restricted-environment-c2f593d19005](https://itnext.io/running-k3s-workload-in-a-restricted-environment-c2f593d19005)