We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
any attempt to start podman VM ends with vfkit error message.
After upgrade (replace ) my MacMini M1 to M4 podman stoped working
Steps to reproduce the issue
$ podman machine init Looking up Podman Machine image at quay.io/podman/machine-os:5.2 to create VM Getting image source signatures Copying blob 12113a444353 done | Copying config 44136fa355 done | Writing manifest to image destination 12113a44435343a5cb2f6fc1c8cb4589b359bafd6123aab0c293e9cf884184ae Extracting compressed file: podman-machine-default-arm64.raw: done Machine init complete To start your machine run: podman machine start $ podman machine start Starting machine "podman-machine-default" Error: vfkit exited unexpectedly with exit code 1
started podman vm on my macos to run my containers
Podman 5.3.1, 5.3.0 and 5.2.5 MacOS Sequoia 15.2 arm64 Apple Silicon M4
No
Rootless
Yes
No response
tested official podman release, homebrew and podman-desktop .. all results same
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Description
any attempt to start podman VM ends with vfkit error message.
After upgrade (replace ) my MacMini M1 to M4 podman stoped working
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
started podman vm on my macos to run my containers
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
tested official podman release, homebrew and podman-desktop .. all results same
The text was updated successfully, but these errors were encountered: