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

netavark (exit code 1): invalid version number starting container #1419

Open
voltagex opened this issue Sep 23, 2023 · 4 comments
Open

netavark (exit code 1): invalid version number starting container #1419

voltagex opened this issue Sep 23, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@voltagex
Copy link

Cockpit version: 300.1-1
Cockpit-podman version: Where do I find this? apt show says Version: 76-1
Podman version:podman version 4.5.1
OS: Debian testing

I can't start any containers. netavark (exit code 1): invalid version number also appears in the UI.

If you let me know

Sep 24 01:32:18 scratch podman[18068]: @ - - [24/Sep/2023:01:32:18 +1000] "GET /v1.12/libpod/containers/f54e6983f4c9540c62f9cc46fd6a7edcc5450544081d19662ea2e2b5a0156f22/logs?follow=true&stdout=true&stderr=true HTTP/1.1" 200 0 "" ""
Sep 24 01:33:28 scratch podman[18161]: [INFO  netavark::firewall] Using iptables firewall driver
Sep 24 01:33:28 scratch podman[18068]: time="2023-09-24T01:33:28+10:00" level=info msg="Request Failed(Internal Server Error): netavark (exit code 1): invalid version number"
Sep 24 01:33:28 scratch podman[18068]: @ - - [24/Sep/2023:01:33:28 +1000] "POST /v1.12/libpod/containers/f54e6983f4c9540c62f9cc46fd6a7edcc5450544081d19662ea2e2b5a0156f22/start? HTTP/1.1" 500 133 "" ""

Steps to reproduce

  1. Install cockpit and cockpit-podman from Debian Testing packages
  2. Start cockpit
  3. Create an alpine container
  4. Try to start it
@voltagex voltagex added the bug Something isn't working label Sep 23, 2023
@jelly
Copy link
Member

jelly commented Sep 25, 2023

Can you start containers from the command line?

I've spun up a testing VM and it all seems to work fine with:

root@debian-testing-127-0-0-2-2201:~# dpkg -l | grep netavark
ii  netavark                             1.4.0-4                        amd64        Rust based network stack for containers
root@debian-testing-127-0-0-2-2201:~# dpkg -l | grep podman
ii  cockpit-podman                       77-1                           all          Cockpit component for Podman containers
ii  podman                               4.6.2+ds1-2                    amd64        tool to manage containers and pods

@voltagex
Copy link
Author

I wonder if all the dependencies are there.

This is my first exposure to podman, I'll have to check later.

Can cockpit warn when critical packages are missing?

@jelly
Copy link
Member

jelly commented Sep 26, 2023

I wonder if all the dependencies are there.

This is my first exposure to podman, I'll have to check later.

Can cockpit warn when critical packages are missing?

It does not warn, it only expects /var/run/podman/podman.sockt.

@voltagex
Copy link
Author

Installed podman and I can run containers from the command line.
Still cannot create and run containers as system from cockpit.

If I create a container on the command line it appears as one owned by my user account and I can start it from cockpit.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants