Closed BlackHole1 closed 1 year ago
Did you only change the image? Because you cannot mount -v /tmp:/tmp
, this is know to be broken: https://github.com/containers/podman/issues/18230
The Fedora CoreOS automatically downloaded by Podman is fedora-coreos-38.20230609.2.1-qemu.x86_64.qcow
. And I also used fedora-coreos-38.20230609.2.1-qemu.x86_64.qcow
when use image-path
.
Did you only change the image? Because you cannot mount
-v /tmp:/tmp
, this is know to be broken: #18230
Thank you for your reply. I try it for now
@Luap99 Following your advice, we have successfully run
. Thank you!
BTW, I would like to know how to obtain detailed logs like the ones you provided in this comment: https://github.com/containers/podman/issues/18230#issuecomment-1554768539
Issue Description
Cannot run container when
machine init
use customimage-path
params.When I do not pass the image-path argument, Podman will automatically download Fedora CoreOS and can run correctly.
Steps to reproduce the issue
Steps to reproduce the issue
./bin/darwin/podman --debug machine init oomol --image-path /Users/black-hole/Downloads/fedora-coreos-38.20230609.2.1-qemu.x86_64.qcow2.xz -v /Users:/Users -v /private:/private -v /Applications:/Applications -v /tmp:/tmp
./bin/darwin/podman --debug start machine oomol
./bin/darwin/podman --debug pull busybox
./bin/darwin/podman --debug run -it --rm busybox sh
Describe the results you received
Describe the results you expected
success run container
podman info output
Additional information