Skip to content

Can oci-archive use a network location? #434

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kolotaev opened this issue Apr 19, 2025 · 1 comment
Open

Can oci-archive use a network location? #434

kolotaev opened this issue Apr 19, 2025 · 1 comment

Comments

@kolotaev
Copy link

kolotaev commented Apr 19, 2025

Hello 👋

Is it possible to make image work with network locations?

Example is:

    task "my-http" {
      driver = "podman"
      config {
        image = "oci-archive:http://10.211.55.9:9999/uploads/myhttp.tar"
      }
    }

Where myhttp.tar is an archive that I serve via HTTP.

I created it via podman save --format oci-archive -o /tmp/uploads/myhttp.tar myhttp:latest.

Note, that podman itself supports getting archive be it filesystem or a network location. Consider this:

podman load -i http://10.211.55.9:9999/uploads/myhttp.tar
Getting image source signatures
Copying blob 99cf8ab899fa skipped: already exists  
Copying blob 41cbe294e54d skipped: already exists  
Copying blob 870027e70bc9 skipped: already exists  
Copying blob fc8a6b71fc5e skipped: already exists  
Copying config 58e9d534e8 done  
Writing manifest to image destination
Storing signatures
Loaded image: myhttp:latest
@mcpherrinm
Copy link

mcpherrinm commented May 14, 2025

As a workaround, I think you can use an artifact block to fetch it, but then note #389 on the image path to pass to podman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants