-
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
error calling ID: runtime error during podman network ls #13183
Comments
The server needs to be 4.0 as well. The api is not backwards compatible |
That makes sense. I'm unsure how to build the full |
#13023 (comment) should help to install it on coreos |
Yes. That fixed it right up. Sorry, I glanced over that, thinking it was unique to M1, but now it makes sense. Thank you. |
I do not know why this code was added but it is wrong. We should never use a plugin dir as config dir. Also this will fail for netavark. The correct default will be set in c/common so podman should not touch it. [NO NEW TESTS NEEDED] Ref containers#13183 Signed-off-by: Paul Holzinger <[email protected]>
I do not know why this code was added but it is wrong. We should never use a plugin dir as config dir. Also this will fail for netavark. The correct default will be set in c/common so podman should not touch it. [NO NEW TESTS NEEDED] Ref containers#13183 Signed-off-by: Paul Holzinger <[email protected]>
I do not know why this code was added but it is wrong. We should never use a plugin dir as config dir. Also this will fail for netavark. The correct default will be set in c/common so podman should not touch it. [NO NEW TESTS NEEDED] Ref containers#13183 Signed-off-by: Paul Holzinger <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I am testing v4.0.0-rc4 with the patched qemu discussed here on mac os. This works and accepts the
volume
options, but I have an issue with networking:That led me to checking the network with
podman network ls
, which yields:Steps to reproduce the issue:
Describe the results you received:
I receive and out of range error (shown above).
Describe the results you expected:
I expected to see a network connection.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
: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
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: