-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fetch directly a ready-to-use image for podman machine on Windows #14698
Comments
@n1hility what say you? |
would be much appreciated #14589 |
That’s definitely where we want to go. Previously this wasn’t an option since we needed to pull from copr to upgrade F35 to podman 4, but now that it’s in f36 it’s doable but it requires that the fedora folks are on board with providing an additional rootfs stream (which receives updates similar to the base we are using today) that has Podman included. |
(I plan to reach out and chat with them about it. I’ll also update the base to f36 soon) |
@Sebbiedu proxy support is high priority for me (expect this sooner than rolling out and consuming the new Fedora stream) |
@n1hility Will work with you on this. We have to collect the list of packages that need to be prepped for sure, hosting location (perhaps pull from a registry; we do this for CRC soon as it allows to re-target an alternative location). |
Have a prepped image that reduces the whole install time to below 1min when the image has been cached, and otherwise can be around 1 - 2 mins depending on the download speed. Still wanna perform some cleanup as at the moment the init still wants to check the image size to determine if complete or cached. This would prevent and airgapped scenario. Alternatively this can be specified with Note: the phrase Note2: update to |
This commit introduces a prepared image for setting up the WSL2 environment. This means that the deployment will take considerable less time to finish (as it does not need to run an update and package install), but also allows to rely on a cached image to re-init the environment without the need for an internet connection. [NO NEW TESTS NEEDED] Signed-off-by: Gerard Braad <[email protected]>
A follow-up issue is to provide better feedback on what is downloaded: At the moment Created as: #15002 |
@n1hility I remember you mentioning updating the man pages as the imagestream is not used (but instead an imagepath). |
This commit introduces a prepared image for setting up the WSL2 environment. This means that the deployment will take considerable less time to finish (as it does not need to run an update and package install), but also allows to rely on a cached image to re-init the environment without the need for an internet connection. [NO NEW TESTS NEEDED] Signed-off-by: Gerard Braad <[email protected]>
(I'm not sure if this is exactly the same issue - but maybe someone can tell?) We're trying to run podman (v. 4.2.1) on a development-machine running Windows without internet connection. (We push files only manually.) Any help how to use completely offline on Windows would be much appreciated. Thanks! |
That sounds like it would be worth a fresh discussion, please open one |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
On macOS, when perfoming
podman machine init
it fetches a pre-builtfedora-coreos-36*-qemu.x86_64.qcow2.xz
file and then it unpacks it and start machine from there.But on Windows, it's fetching a
fedora-35-x86_64.tar.xz
file and then we're entering in updates/installation of RPM packages.I would expect to have a ready-to-use image, and not going to the process of updating/installing standalone RPM files.
In case of offline mode, I can't do
podman machine init
step even if I've locally thefedora-35-x86_64.tar.xz
file.Also it's taking a very long time to perform all these small update/install process.
And creating another machine, we go to all these steps again and again.
Steps to reproduce the issue:
podman machine init
on Windowscreates another machine,
podman machine init foo
it'll try to install packages, etc again.
Describe the results you received:
Installing packages, updating fedora, etc.
Describe the results you expected:
Just boot the prebuilt VM, ready-to-use, no need to have post-start actions
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):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/No
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: