kubedock icon indicating copy to clipboard operation
kubedock copied to clipboard

Published 20 hours ago • verified publisher icon joyrex2001

Podman support

Open l0rd opened this issue 2 years ago • 5 comments

Problem Description

When trying to run podman on a host where I have started kubedock I get the following error

$ podman --remote --url "tcp://127.0.0.1:2475" run --name httpd -d -p 8080:8080 python python -m http.server 8080
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 socket: ping response was 404

And from kubedock logs

image

How to reproduce it

The issue can be reproduced on OpenShift Developer Sandbox (a Red Hat Developer account is required but it's free) using the following link: https://workspaces.openshift.com/f?url=https://github.com/l0rd/micronaut-sample

Video recording

https://user-images.githubusercontent.com/606959/232914999-8a171ca7-67ea-401c-83cf-a614d1f76c34.mp4

l0rd avatar Apr 18 '23 22:04 l0rd

Initial work has been started where podman routes can be implemented here, adjacent to the docker api implementation.

joyrex2001 avatar Apr 30 '23 19:04 joyrex2001

Initial work has been started where podman routes can be implemented here, adjacent to the docker api implementation.

Amazing. I have been testing a simple podman run and the pod got created successfully. I have also tested with podman run -ti busybox and podman run -d -P httpd but the first didn't start and the second didn't expose any port (which is perfectly fine for an initial support).

l0rd avatar May 02 '23 16:05 l0rd

I just released 0.11.0 which supports:

  • podman run (with port mappings and volumes, not interactive mode)
  • podman ps (does not show mapped ports)
  • podman exec (not interactive mode)
  • podman cp (gives an error when copying from container to host, but did the actual copy)
  • podman logs, inspect, kill, rm, wait, stop, start

joyrex2001 avatar May 24 '23 11:05 joyrex2001

Hi @joyrex2001

I noticed that 'podman generate kube' didn't work with kubedock. Kubedock logs showed 404, which suggests the feature is simply not implemented.

Since this GH issue is about general podman support, would it be OK to add "podman generate kube" requirement as part of this ticket?

agiertli avatar Jul 25 '23 17:07 agiertli

@agiertli yes, makes sense to track it in this ticket (sorry for the late reply).

I just released 0.13.0, which means for podman support:

  • added support for podman exec interactive mode
  • added support for podman restart
  • fixed podman cp error
  • fixed podman ps ports

joyrex2001 avatar Sep 06 '23 19:09 joyrex2001