Use with local container images

[ericcurtin]

I have built an image locally for usage with podman-bootc, I have no desire to push it anywhere. I have placed this image in both rootfull and rootless container storage locations just in case. When I do this:

$ podman-bootc run localhost/bootc

It tries to pull and fails:

Trying to pull localhost/bootc:latest...
Error: unable to install bootc image: failed to pull image: internal error: unable to copy from source docker://localhost/bootc:latest: initializing source docker://localhost/bootc:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

[ericcurtin]

Maybe it's something like this:

sudo podman save localhost/bootc | podman -c podman-machine-default-root load

[ericcurtin]

The workflow I am trying to achieve is use the same container image as a base for my host OS, containers and VMs (so I can test all three kinds of scenarios). All based on the same Containerfile I build locally on the same machine.

A bonus would be to try and share the container image stores as much as possible for de-duplication purposes, but I can copy it around using things like:

podman save | podman load

if needs be...

[cgwalters]

I have placed this image in both rootfull and rootless container storage locations just in case.

Aren't you just hitting #10 and #95 etc?

sudo podman save localhost/bootc | podman -c podman-machine-default-root load

Yeah things like that are obviously terrible and are what we're aiming to fix with issues like the above.

[ericcurtin]

I have placed this image in both rootfull and rootless container storage locations just in case.

Aren't you just hitting #10 and #95 etc?

I guess... Happy to close...

sudo podman save localhost/bootc | podman -c podman-machine-default-root load

Yeah things like that are obviously terrible and are what we're aiming to fix with issues like the above.