'podman pull' cache downloaded blobs temporarily

[sify21]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

podman pull images by pulling its blobs. In case of network error, this situation may happen: most blobs are downloaded, but some timed out. In this case, the next pull will copy all blobs again. It's better that downloaded blobs are cached in a temporary place, then next pull will use the cache and save time.

Steps to reproduce the issue:

1.podman pull a image

2.a network error occurs. for example network timeout.

Describe the results you received:
next pull will copy all blobs again

Describe the results you expected:
next pull can use previously downloaded blob's cache

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:            1.8.0
RemoteAPI Version:  1
Go Version:         go1.12.15
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.12.15
  podman version: 1.8.0
host:
  BuildahVersion: 1.13.1
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.10-2.fc30.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.10, commit: 35d9b09d9d2791c7167091a9f25792535a380967'
  Distribution:
    distribution: fedora
    version: "30"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree: 1448787968
  MemTotal: 16659460096
  OCIRuntime:
    name: runc
    package: runc-1.0.0-102.dev.gitdc9208a.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: ffa084d279c26351e6e63bd2c3f28d43fa1f6e57
      spec: 1.0.1-dev
  SwapFree: 8587034624
  SwapTotal: 8589930496
  arch: amd64
  cpus: 8
  eventlogger: journald
  hostname: sify21
  kernel: 5.5.8-100.fc30.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-4.git19d199a.fc30.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.2
      commit: 19d199a6ca424fcf9516320a327cedad85cf4dfb
  uptime: 31h 35m 58.07s (Approximately 1.29 days)
registries:
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /home/sify21/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.5-2.fc30.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7.5
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /home/sify21/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 9
  RunRoot: /run/user/1000
  VolumePath: /home/sify21/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.8.0-4.fc30.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):

[vrothberg]

Thanks for opening the issue! containers/image#611 will address the issue as the blobs will be committed to the storage as soon as possible. containers/image#611 is quite dusty but we will break the big changes into smaller ones in the near future.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

@vrothberg Is it the future yet? :^)

[rhatdan]

@vrothberg Ping

[vrothberg]

I'd love to start working on containers/image#611 but that's something we must prioritize so that I actually have time to.

[rhatdan]

Has this bubbled up in priority yet?

[rhatdan]

Still want to move forward on this one.

[vrothberg]

Still want to move forward on this one.

You have the power to increase priority :)

[rhatdan]

Lets talk about this tomorrow at Watercooler.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[vrothberg]

I am closing this issue in favor of #7497. It's still on the radar and we'll tackle it soon.