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.

Sign up for GitHub

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

Jump to bottom

Podman: json: cannot unmarshal object into Go value of type []podman.portMapping #1734

Closed
AkihiroSuda opened this issue Jul 15, 2020 · 5 comments
Closed

Podman: json: cannot unmarshal object into Go value of type []podman.portMapping #1734

AkihiroSuda opened this issue Jul 15, 2020 · 5 comments
Assignees
@giuseppe
Labels
kind/external upstream bugs lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.

Comments

@AkihiroSuda
Copy link
Member

What happened:

$ sudo KIND_EXPERIMENTAL_PROVIDER=podman kind create cluster
using podman due to KIND_EXPERIMENTAL_PROVIDER
enabling experimental podman provider
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.18.4) 🖼 
 ✓ Preparing nodes 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾
ERROR: failed to create cluster: invalid network details: json: cannot unmarshal object into Go value of type []podman.portMapping

What you expected to happen:

Should work

How to reproduce it (as minimally and precisely as possible):
See above

Anything else we need to know?:

Environment:
@AkihiroSuda AkihiroSuda added the kind/bug Categorizes issue or PR as related to a bug. label Jul 15, 2020
@AkihiroSuda
Copy link
Member Author

seems being fixed in #1728

@BenTheElder
Copy link
Member

This is a podman breakage imho, dealing with networking in podman has been .. frustrating.

@BenTheElder BenTheElder added kind/external upstream bugs and removed kind/bug Categorizes issue or PR as related to a bug. labels Jul 15, 2020
@BenTheElder BenTheElder added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Jul 15, 2020
@giuseppe
Copy link
Member

fixed by #1728

@giuseppe
Copy link
Member

we can close this issue (I've no privileges for doing it)

@AkihiroSuda
Copy link
Member Author

Thanks!

@BenTheElder BenTheElder mentioned this issue Jul 16, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@giuseppe giuseppe

Labels
kind/external upstream bugs lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@giuseppe @BenTheElder @AkihiroSuda