Skip to content
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

Create Image without Internet connection on Windows #15995

Closed
brainbytes42 opened this issue Sep 29, 2022 · 12 comments · Fixed by #17266
Closed

Create Image without Internet connection on Windows #15995

brainbytes42 opened this issue Sep 29, 2022 · 12 comments · Fixed by #17266
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. windows issue/bug on Windows

Comments

@brainbytes42
Copy link

[Thanks @mheon for your quick reply @ #14698!]

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

/kind bug (... I think?)

Description

We're trying to run podman (v. 4.2.1) on a development-machine running Windows 10 / WSL without internet connection. (We can push files only manually.)
Even when using a local --image-path, it wouldn't work, as it tries to download several packages on machine init or says it has a directory(?!).

Any help how to use completely offline on Windows would be much appreciated. Thanks!

Steps to reproduce the issue:

C:\>podman machine init

Describe the results you received:

Error: head request failed: https://github.com/containers/podman-wsl-fedora/releases/latest/download/rootfs.tar.xz: Head "https://github.com/containers/podman-wsl-fedora/releases/latest/download/rootfs.tar.xz": dial tcp: lookup github.com: no such host

Or for a local image (Or did I mess it up here? New to podman...):

C:\>podman machine init --image-path "C:\Austausch\rootfs.tar.xz"
Error: open C:\Users\adminois\.local\share\containers\podman\machine\wsl\cache: is a directory

C:\>podman machine init --image-path "C:\Austausch\fedora-coreos-36.20220522.1.0-qemu.aarch64.qcow2.xz"
Error: open C:\Users\adminois\.local\share\containers\podman\machine\wsl\cache: is a directory

Describe the results you expected:
Podman-magic :-)

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

Output of podman version:

It is Version 4.2.1, but the output is:

C:\>podman version
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: Get "http://d/v4.2.1/libpod/_ping": dial unix ///run/podman/podman.sock: connect: Ein ungültiges Argument wurde angegeben.

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

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

Physical machine, Win 10 + WSL

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2022

@brainbytes42: The label(s) kind/, kind/, kind/(..., kind/i, kind/think?) cannot be applied, because the repository doesn't have them.

In response to this:

[Thanks @mheon for your quick reply @ #14698!]

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

/kind bug (... I think?)

Description

We're trying to run podman (v. 4.2.1) on a development-machine running Windows 10 / WSL without internet connection. (We can push files only manually.)
Even when using a local --image-path, it wouldn't work, as it tries to download several packages on machine init or says it has a directory(?!).

Any help how to use completely offline on Windows would be much appreciated. Thanks!

Steps to reproduce the issue:

C:\>podman machine init

Describe the results you received:

Error: head request failed: https://github.com/containers/podman-wsl-fedora/releases/latest/download/rootfs.tar.xz: Head "https://github.com/containers/podman-wsl-fedora/releases/latest/download/rootfs.tar.xz": dial tcp: lookup github.com: no such host

Or for a local image (Or did I mess it up here? New to podman...):

C:\>podman machine init --image-path "C:\Austausch\rootfs.tar.xz"
Error: open C:\Users\adminois\.local\share\containers\podman\machine\wsl\cache: is a directory

C:\>podman machine init --image-path "C:\Austausch\fedora-coreos-36.20220522.1.0-qemu.aarch64.qcow2.xz"
Error: open C:\Users\adminois\.local\share\containers\podman\machine\wsl\cache: is a directory

Describe the results you expected:
Podman-magic :-)

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

Output of podman version:

It is Version 4.2.1, but the output is:

C:\>podman version
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: Get "http://d/v4.2.1/libpod/_ping": dial unix ///run/podman/podman.sock: connect: Ein ungültiges Argument wurde angegeben.

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

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

Physical machine, Win 10 + WSL

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Luap99 Luap99 added the windows issue/bug on Windows label Sep 29, 2022
@n1hility
Copy link
Member

n1hility commented Sep 29, 2022

@cdoern want to take a look at this one? This issue is that image-path is not properly handling absolute paths.

Relative works (// cc @brainbytes42 for a workaround)

podman machine init --image-path .\rootfs.tar.xz

@cdoern
Copy link
Contributor

cdoern commented Sep 30, 2022

sure @n1hility ! I will take a look

@brainbytes42
Copy link
Author

Thanks a lot @n1hility, your workaround saved my day! :-)

Relative works (// cc @brainbytes42 for a workaround)

podman machine init --image-path .\rootfs.tar.xz

@github-actions
Copy link

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

@rhatdan
Copy link
Member

rhatdan commented Nov 21, 2022

@cdoern did you ever work on this?

@cdoern
Copy link
Contributor

cdoern commented Nov 21, 2022

@rhatdan no not yet, I might look at it this week since I have more time and will be home at my windows machine

@github-actions
Copy link

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

@rhatdan
Copy link
Member

rhatdan commented Dec 22, 2022

@cdoern @n1hility anyone have time to fix his one up?

@github-actions
Copy link

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

@rhatdan
Copy link
Member

rhatdan commented Jan 23, 2023

@n1hility any progress?

@n1hility
Copy link
Member

n1hility commented Jan 24, 2023

@rhatdan was saving this one for @cdoern. Although since he's likely not avail will look at it this week.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. windows issue/bug on Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants