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

error adding pod to CNI network "podman": unexpected end of JSON input #11996

Closed
nevotheless opened this issue Oct 15, 2021 · 9 comments
Closed
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.

Comments

@nevotheless
Copy link

nevotheless commented Oct 15, 2021

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Steps to reproduce the issue:

  1. brew install podman

  2. podman machine init

  3. podman machine start

  4. Rodman run hello-world

Describe the results you received:

Error: error preparing container 3007ab3e8cb688ea22793345e480fd8e707f4334a73a936a4725d06ce10db746 for attach: error configuring network namespace for container 3007ab3e8cb688ea22793345e480fd8e707f4334a73a936a4725d06ce10db746: error adding pod musing_dewdney_musing_dewdney to CNI network "podman": unexpected end of JSON input

Describe the results you expected:
I expected the output of the hello-world container.

Additional information you deem important (e.g. issue happens only occasionally):
kubernetes/minikube#12581 is having the same issue.
I've also had a cgroupv2 related issue a couple of days ago maybe this relates to cgroup as well somehow.

Output of podman version:

Client:
Version:      3.4.0
API Version:  3.4.0
Go Version:   go1.17.2
Built:        Thu Sep 30 20:44:31 2021
OS/Arch:      darwin/arm64

Server:
Version:      3.3.1
API Version:  3.3.1
Go Version:   go1.16.6
Built:        Mon Aug 30 22:45:47 2021
OS/Arch:      linux/arm64

Output of podman info --debug:

host:
  arch: arm64
  buildahVersion: 1.22.3
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.29-2.fc34.aarch64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.29, commit: '
  cpus: 1
  distribution:
    distribution: fedora
    version: "34"
  eventLogger: journald
  hostname: localhost
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.14.9-200.fc34.aarch64
  linkmode: dynamic
  logDriver: ""
  memFree: 756273152
  memTotal: 2050326528
  ociRuntime:
    name: crun
    package: crun-1.0-1.fc34.aarch64
    path: /usr/bin/crun
    version: |-
      crun version 1.0
      commit: 139dc6971e2f1d931af520188763e984d6cdfbf8
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.12-2.fc34.aarch64
    version: |-
      slirp4netns version 1.1.12
      commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 0
  swapTotal: 0
  uptime: 12m 48.64s
plugins:
  log: null
  network: null
  volume: null
registries:
  search:
  - docker.io
store:
  configFile: /var/home/core/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 0
    stopped: 4
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/core/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 2
  runRoot: /run/user/1000/containers
  volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
  APIVersion: 3.3.1
  Built: 1630356347
  BuiltTime: Mon Aug 30 20:45:47 2021
  GitCommit: ""
  GoVersion: go1.16.6
  OsArch: linux/arm64
  Version: 3.3.1

Package info (e.g. output of rpm -q podman or apt list podman):

podman: stable 3.4.0 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/opt/homebrew/Cellar/podman/3.4.0_2 (170 files, 40.4MB) *
  Poured from bottle on 2021-10-15 at 23:09:21
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go ✘, go-md2man ✘
Required: qemu ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
zsh completions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> Analytics
install: 12,574 (30 days), 25,993 (90 days), 52,585 (365 days)
install-on-request: 12,569 (30 days), 25,986 (90 days), 52,474 (365 days)
build-error: 0 (30 days)

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 (13", M1, 2020) MacOS 11.6 (20G165)

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 15, 2021
@jgowdy
Copy link

jgowdy commented Oct 15, 2021

I am experiencing this same issue on macOS, both x64 and arm64.

I removed Docker Desktop, Rancher Desktop, removed podman, rm -rf ~/.config/containers ~/.local/share/containers ~/.docker, and rebooted. Reinstalled podman, podman machine init, podman machine start, podman run -it alpine sh and got the same result.

@afbjorklund
Copy link
Contributor

afbjorklund commented Oct 15, 2021

Same as:

@mheon
Copy link
Member

mheon commented Oct 17, 2021

Closing as a dupe

@mheon mheon closed this as completed Oct 17, 2021
@afbjorklund
Copy link
Contributor

You might want to add something to the home page, to avoid all these duplicate error reports ?

https://podman.io/getting-started/installation

@cheyang0323
Copy link

I am experiencing this same issue on macOS on the x64

❯ podman version
Client:
Version: 3.4.0
API Version: 3.4.0
Go Version: go1.17.2
Built: Fri Oct 1 02:44:31 2021
OS/Arch: darwin/amd64

Server:
Version: 3.3.1
API Version: 3.3.1
Go Version: go1.16.6
Built: Tue Aug 31 04:46:36 2021
OS/Arch: linux/amd64

@mheon
Copy link
Member

mheon commented Oct 18, 2021

We have a troubleshooting doc, that seems like an appropriate place.

@mfouesneau
Copy link

Sorry but what the actual fix?

@afbjorklund
Copy link
Contributor

Sorry but what the actual fix?

The fixes come every fortnight, so the workaround is to pick a pre-release from the "devel" stream: #11837 (comment)

@mfouesneau
Copy link

Cannot connect to Podman. Please verify your connection to the Linux system using podman system connection list, or try podman machine init and podman machine start to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: Connection to bastion host (ssh://core@localhost:56781/run/user/1000/podman/podman.sock) failed.: dial tcp [::1]:56781: connect: connection refused

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
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.
Projects
None yet
Development

No branches or pull requests

6 participants