Skip to content
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

Unable to init podman machine on mac with provider applehv due to truncate missing #21065

Closed
adrianriobo opened this issue Dec 20, 2023 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine macos MacOS (OSX) related stale-issue

Comments

@adrianriobo
Copy link

Issue Description

Trying to start a podman machine on macos with applehv it ends up on error due to missing truncate tool

Steps to reproduce the issue

Steps to reproduce the issue

  1. export CONTAINERS_MACHINE_PROVIDER= applehv
  2. podman machine init

Describe the results you received

podman machine init ends up failing with:

Extracting compressed file: podman-machine-default_fedora-coreos-39.20231204.2.1-applehv.x86_64.raw: done  
Error: exec: "truncate": executable file not found in $PATH

Describe the results you expected

podman machine is properly initialized

podman info output

podman v4.8.2 installed from pkg

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@adrianriobo adrianriobo added the kind/bug Categorizes issue or PR as related to a bug. label Dec 20, 2023
@cfergeau
Copy link
Contributor

Probably a good reason to revert the pkg/machine/applehv changes in 33a92aa
If I remember correctly, the external truncate command had the same performance issues in some corner cases.

@rhatdan
Copy link
Member

rhatdan commented Dec 21, 2023

Should we use truncate if it is found and then fall back to slower mechanism?

@gbraad
Copy link
Member

gbraad commented Dec 21, 2023

Agree. While we can assume these are mostly on development machines, not everyone will have xcode installed.

@cfergeau
Copy link
Contributor

I think the external command had the same issues, not sure a fallback is worth it.

@rhatdan
Copy link
Member

rhatdan commented Dec 22, 2023

I thought the porblem was if the external command does not exist, the fall back is not executed?

@Luap99 Luap99 added macos MacOS (OSX) related machine labels Jan 3, 2024
Copy link

github-actions bot commented Feb 3, 2024

A friendly reminder that this issue had no activity for 30 days.

@Luap99
Copy link
Member

Luap99 commented Apr 4, 2024

I don't see truncate being used in the 5.0 code so I assume this is fixed

@Luap99 Luap99 closed this as completed Apr 4, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jul 5, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Jul 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine macos MacOS (OSX) related stale-issue
Projects
None yet
Development

No branches or pull requests

5 participants