melodic-hamburger-2332906/09/2022, 1:42 PM
)? If I leave it out, I get correct behavior, though.
fast-garage-6609306/09/2022, 4:38 PM
. The option exists to export the image somewhere else instead of importing it into the runtime.
melodic-hamburger-2332906/09/2022, 4:42 PM
The image exporter writes the build result as an image or a manifest list. When using docker driver the image will appear in docker images. Optionally, image can be automatically pushed to a registry by specifying attributes.
in Docker mode (when using buildx) makes the image available locally. However, in containerd mode, the command just finishes silently and there’s no image anywhere. My point is; it seems that `nerdctl build`’s behavior unexpectedly differs from
even though the APIs are very similar. It would help avoid confusion if the APIs matched in expected behavior.
docker buildx build
fast-garage-6609306/09/2022, 4:57 PM
parameter and pushes to the
repository instead @best-accountant-68201 :
$ nerdctl build -t registry.home/hi:there --output type=image,name=registry.home/wazzup:yo,push=true . [+] Building 0.6s (7/7) FINISHED => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 68B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for <http://docker.io/library/busybox:latest|docker.io/library/busybox:latest> 0.4s => [1/2] FROM <http://docker.io/library/busybox@sha256:3614ca5eacf0a3a1bcc361c939202a974b4902b9334ff36eb29ffe9011aaad83|docker.io/library/busybox@sha256:3614ca5eacf0a3a1bcc361c939202a974b4902b9334ff36eb29ffe9011aaad83> 0.0s => => resolve <http://docker.io/library/busybox@sha256:3614ca5eacf0a3a1bcc361c939202a974b4902b9334ff36eb29ffe9011aaad83|docker.io/library/busybox@sha256:3614ca5eacf0a3a1bcc361c939202a974b4902b9334ff36eb29ffe9011aaad83> 0.0s => CACHED [2/2] RUN touch /wazzup 0.0s => exporting to image 0.1s => => exporting layers 0.0s => => exporting manifest sha256:0012dd04372a9a766eba420c0a7aa2ad91bd4b3ef248111e383fe2ae8e77c920 0.0s => => exporting config sha256:c7be383d61fc802cad6de5f81d27a72d49d3f921137c3e1919f6dded7060fa74 0.0s => => naming to registry.home/hi:there 0.0s => => pushing layers 0.1s => => pushing manifest for registry.home/hi:there@sha256:0012dd04372a9a766eba420c0a7aa2ad91bd4b3ef248111e383fe2ae8e7 0.0s => [auth] sharing credentials for registry.home 0.0s $ nerdctl images REPOSITORY TAG IMAGE ID CREATED PLATFORM SIZE BLOB SIZE rancher/rancher latest ae5135c25b21 39 hours ago linux/amd64 1.5 GiB 434.2 MiB
locally and also push it to
, but it didn't create any local image, and pushed to the former rather than the latter repo name.
melodic-hamburger-2332906/09/2022, 5:01 PM
fast-garage-6609306/09/2022, 5:01 PM
melodic-hamburger-2332906/09/2022, 5:03 PM
doesn’t seem to work.
fast-garage-6609306/09/2022, 5:14 PM
doesn't actually run on macOS, this is maybe not too surprising. You could run the build inside the VM, so instead of
, but note that I haven't done it. You will need to install the required tools into the VM, like
rdctl shell make binaries
and whatever else may be needed (like
rdctl shell sudo apk add go
rdctl shell sudo apk add git go make rdctl shell make binaries
$ rdctl shell sudo _output/nerdctl --version nerdctl version 0.20.0-38-gb702a25
if you want the Rancher Desktop
wrapper to use it automatically
$ rdctl shell sudo _output/nerdctl --address /run/k3s/containerd/containerd.sock images REPOSITORY TAG IMAGE ID CREATED PLATFORM SIZE BLOB SIZE rancher/rancher latest ae5135c25b21 39 hours ago linux/amd64 1.5 GiB 434.2 MiB
melodic-hamburger-2332906/10/2022, 3:12 AM
fast-garage-6609306/10/2022, 5:29 AM
best-accountant-6820106/10/2022, 6:09 AM