Closed etenzy closed 2 years ago
are you saying that podman machine failed to init? or subsequent podman commands do not work.
podman machine fails to init because it calls dd
on Apple silicon.
if coreutils are installed dd
is linked to a GNU version of dd, which only accepts uppercase units which results in an error.
imho the solution would be to call the system dd directly via /bin/dd
(see my pr)
Installing GNU tools without the "g" prefix breaks all kinds of stuff
Installing GNU tools without the "g" prefix breaks all kinds of stuff
right, that's a thing about how brew deals with coreutils... so i thought we could use the system's dd exclusively, because /bin/dd shouldn't go anywhere
Makes sense to me.
/kind bug
Description
podman machine does not create/start when coreutils are installed on mac
Steps to reproduce the issue:
brew install coreutils
podman machine init
Describe the results you received:
Describe the results you expected: podman machine to be initialized
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman --version
:Output of
podman info --debug
:Package info
brew list
:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
MacBook Pro (14-inch, 2021) Chip: Apple M1 Pro Memory: 32 GB macOS Monterey: 12.0.1 (21A559)
Tested Workaround:
Possible causes: https://github.com/containers/podman/blob/8430ffc72e74f1271174984674a1c2ee6118779e/pkg/machine/qemu/options_darwin_arm64.go#L25-L29