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

Possible regression with podman system service #12309

Closed
rod260185 opened this issue Nov 16, 2021 · 0 comments
Closed

Possible regression with podman system service #12309

rod260185 opened this issue Nov 16, 2021 · 0 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@rod260185
Copy link

I have the same problem now, with this configuration:
host:
arch: amd64
buildahVersion: 1.23.1
cgroupControllers:

  • cpuset
  • cpu
  • io
  • memory
  • hugetlb
  • pids
  • rdma
  • misc
    cgroupManager: systemd
    cgroupVersion: v2
    conmon:
    package: conmon-2.0.30-1.1.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.30, commit: unknown'
    cpus: 4
    distribution:
    distribution: '"opensuse-microos"'
    version: "20211107"
    eventLogger: journald
    hostname: ev00000895
    idMappings:
    gidmap: null
    uidmap: null
    kernel: 5.14.14-1-default
    linkmode: dynamic
    logDriver: journald
    memFree: 11157291008
    memTotal: 20200374272
    ociRuntime:
    name: runc
    package: runc-1.0.2-1.2.x86_64
    path: /usr/bin/runc
    version: |-
    runc version 1.0.2
    spec: 1.0.2-dev
    go: go1.13.15
    libseccomp: 2.5.2
    os: linux
    remoteSocket:
    exists: true
    path: /run/podman/podman.sock
    security:
    apparmorEnabled: true
    capabilities: CAP_AUDIT_WRITE,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_MKNOD,CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: false
    seccompEnabled: true
    seccompProfilePath: /etc/containers/seccomp.json
    selinuxEnabled: false
    serviceIsRemote: false
    slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.11-1.2.x86_64
    version: |-
    slirp4netns version 1.1.11
    commit: unknown
    libslirp: 4.6.1
    SLIRP_CONFIG_VERSION_MAX: 3
    libseccomp: 2.5.2
    swapFree: 0
    swapTotal: 0
    uptime: 4m 7.01s
    plugins:
    log:
  • k8s-file
  • none
  • journald
    network:
  • bridge
  • macvlan
    volume:
  • local
    registries:
    search:
  • registry.opensuse.org
  • docker.io
    store:
    configFile: /etc/containers/storage.conf
    containerStore:
    number: 27
    paused: 0
    running: 24
    stopped: 3
    graphDriverName: btrfs
    graphOptions: {}
    graphRoot: /var/lib/containers/storage
    graphStatus:
    Build Version: 'Btrfs v5.14.1 '
    Library Version: "102"
    imageStore:
    number: 235
    runRoot: /run/containers/storage
    volumePath: /var/lib/containers/storage/volumes
    version:
    APIVersion: 3.4.1
    Built: 1634688000
    BuiltTime: Tue Oct 19 21:00:00 2021
    GitCommit: ""
    GoVersion: go1.13.15
    OsArch: linux/amd64
    Version: 3.4.1

It seems to be some kind of regression. Though my problem comes with the use of docker extension of VSCode, which is inspecting the api through the podman.sock.

Originally posted by @rod260185 in #7946 (comment)

@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
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

1 participant