Replies: 5 comments
-
|
Can you update your MAC to 12.4 release. This is a known issue between QEMU and Mac. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for triaging, @rhatdan! Unfortunately, I cannot upgrade to 12.4, as this is a work computer and we have a policy that restricts upgrades to approved versions. I think this policy was put in place because previous upgrades broke some of the software we use. It seems I can work around this by downgrading to the prior version of CoreOS, do you know the latest version that I should use? I suppose the one prior to the inclusion of qemu-user-static might work, and I'll have to try the upgrade again in a few months once I have 12.4 installed |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, #14563 is what made things break for 12.3, so another workaround could be to undo the changes seen in the PR in your |
Beta Was this translation helpful? Give feedback.
-
|
@shanesmith Amazing, thanks for this workaround! I can confirm that it works on my 12.3.1 machine. |
Beta Was this translation helpful? Give feedback.
-
|
Since this is little Podman itself can do to fix this. I am switching this to a discussion rather than an issue. |
Beta Was this translation helpful? Give feedback.
-
/kind bug
Description
When running
podman machine start, I see a dialog pop up to allow permissions for gvproxy and then a pink screen. This seems to be a kernel panic as once my machine restarts, I get the option to submit a crash report to Apple.I'm not sure whether the issue is in podman or (it seems more likely) CoreOS, so I'm filing here to triage. cc @dustymabe
Steps to reproduce the issue:
Upgrade to latest podman-machine-default (I wanted to try the latest CoreOS as it includes qemu-user-static)
Run
podman machine startFireworks 🙃
Describe the results you received:
A kernel panic
Describe the results you expected:
I expected podman machine to start normally
Additional information you deem important (e.g. issue happens only occasionally):
I can reproduce this at-will, and unfortunately this makes podman unusable for me. I was previously running CoreOS 35 without issue, so I could try rolling back, but running containers locally isn't that important to me, so it's something I can investigate later.
Output of
podman machine inspect podman-machine-default:[ { "ConfigPath": { "Path": "/Users/jawnsy/.config/containers/podman/machine/qemu/podman-machine-default.json" }, "Created": "2022-07-09T08:49:44.815738-07:00", "Image": { "IgnitionFilePath": { "Path": "/Users/jawnsy/.config/containers/podman/machine/qemu/podman-machine-default.ign" }, "ImageStream": "testing", "ImagePath": { "Path": "/Users/jawnsy/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-36.20220703.2.1-qemu.aarch64.qcow2" } }, "LastUp": "2022-07-09T08:49:44.815738-07:00", "Name": "podman-machine-default", "Resources": { "CPUs": 1, "DiskSize": 100, "Memory": 2048 }, "SSHConfig": { "IdentityPath": "/Users/jawnsy/.ssh/podman-machine-default", "Port": 49340, "RemoteUsername": "core" }, "State": "" } ]Output of
podman version:Can't run podman version, since I can't start things:
However, I did run
podman -v(podman is installed usingbrew):Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Crash report
Other system info that may be relevant:
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.):
Beta Was this translation helpful? Give feedback.
All reactions