Uploaded image for project: 'Container Tools'
  1. Container Tools
  2. RUN-2234

[containers/podman] Podman-machine default installer, won't resolve/progress on a download issue (lost connection, incomplete file...)

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • rhel-sst-container-tools
    • RUN 259

      [2338467517] Upstream Reporter: Peyman Borhani
      Upstream issue status: Closed
      Upstream description:

      Bug description

      When initializing podman-desktop, the installer is building a default-machine.

      A file download process took long (maybe a connection issue), so I exit it. On the next retry, it results in: error: exit code 125

      In terminal executing podman machine init resulted in unable to extract and unexpected EOF error.

      This lead me to find-delete downloaded file, which solved the issue, and installer completed on the next try.

      My assumption is podman or podman-desktop app not making a download completion/verification record, and therefore not deleting/overwriting it on next attempts, instead it tries to extract the incomplete file.

      Is best if the file is checked and verified, before extraction, and if not retry overwrite invalid file.

      Thanks.

      Operating system

      Windows 10 x64 (ver 22H2 / Build 19045.4412)

      Installation Method

      Installer from website/GitHub releases

      Version

      1.10.2

      Steps to reproduce

      Break the download in default machine install process. (or corrupt the file)

      Relevant log output

      $ podman machine init
      time="2024-05-28T10:11:56+03:30" level=error msg="Error extracting compressed file: "unexpected EOF""
      Error: unexpected EOF
      
      ### Additional context
      
      _No response_
      

      Upstream URL: https://github.com/containers/podman/issues/22927

              nsella@redhat.com Nicola Sella
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: