-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman v5.0.0-RC4 Machine init command results in error cannot find policy.json #21964
Comments
you can get the policy.json from several locations; but https://github.com/containers/podman/blob/main/pkg/machine/ocipull/policy.json is one |
fwiw, rc5's installer should have the policy.json in it right @n1hility @ashley-cui ? |
not yet, will get to it soon though |
When we set a relative path (i.e. ".") it should be resolved next to binary so we need to get the base dir. If we join it directly like it did before you get a path like .../podman/policy.json where podman is the podman executable so it is not a directory and thus could not contain the policy.json file. ref containers#21964 Signed-off-by: Paul Holzinger <[email protected]>
The relative path is definitely wrong though, I created #21971 for it. |
@baude @Luap99 Thanks for looking into it.
Should I continue in this issue or create new one? |
Sounds like a different issue, seems like you over the policy.json error so I consider this fixed. |
@Luap99 Ok, also colleague was able to reproduce the issue I first saw with rc5 but could not reproduce after manually creating a
|
Sound like #21985 didn't work then as it no longer set's the build option for some reason. Can you at least verify if policy.json was put into |
Yes the |
I can confirm the release binaries were somehow created without MACHINE_POLICY* set, looking into why |
Just a follow up the issue appears to be specific to the environment the podman binary was built on (the go linker failed to interpret all specified X ldflags, including other values we set on build like the git sha Will update the issue later with next steps. |
How are the zip files for the releases build, @ashley-cui @lsm5 @mheon? |
@ashley-cui was this fixed in the rc from yesterday ? |
Yep, should be. |
Issue Description
podman machine init
command with podman v5.0.0-rc4 bits on windows with hyperv throws an error:Related issue: #21855
Steps to reproduce the issue
Steps to reproduce the issue
CONTAINERS_MACHINE_PROVIDER
tohyperv
podman machine init
Describe the results you received
Describe the results you expected
Podman machine created
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Windows 10 Professional
CONTAINERS_MACHINE_PROVIDER=hyperv
Additional information
Whole command run with debugging on:
The text was updated successfully, but these errors were encountered: