Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-70516

docker-work-flow-plugin failed with Podman will fail when "podman top -eo pid, comm",

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • docker-workflow-plugin
    • None
    • OCP environment(Red Hat OpenShift Container Platform)

          [JENKINS-70516] docker-work-flow-plugin failed with Podman will fail when "podman top -eo pid, comm",

          Mark Waite added a comment -

          As far as I understand it, the docker-workflow plugin does not support podman. There are use cases where podman is compatible with docker, but they are definitely not the same product and unless there is an explicit statement of support for podman, I don't think it should be assumed that it will work.

          Mark Waite added a comment - As far as I understand it, the docker-workflow plugin does not support podman . There are use cases where podman is compatible with docker , but they are definitely not the same product and unless there is an explicit statement of support for podman , I don't think it should be assumed that it will work.

          ronghai added a comment - - edited

          Hello, thanks for reply, so far, I am trying the use case that jenkins agent nodes could use both docker based openstack node and podman based for ocp node. It works well as podman compatibles with docker. Seems only in this case, the issue here is only as code mentioned,

          LaunchResult result = launch(launchEnv, false, "top", containerId, "-eo", "pid,comm");
          

          with "-eo" works for docker and "eo" works for podman.

          Would be possible to have improvement for this minor change for this hardcoded "-eo? not for explicit support podman, but some clean way can bypass this issue"?

          ronghai added a comment - - edited Hello, thanks for reply, so far, I am trying the use case that jenkins agent nodes could use both docker based openstack node and podman based for ocp node. It works well as podman compatibles with docker. Seems only in this case, the issue here is only as code mentioned, LaunchResult result = launch(launchEnv, false , "top" , containerId, "-eo" , "pid,comm" ); with "-eo" works for docker and "eo" works for podman. Would be possible to have improvement for this minor change for this hardcoded "-eo? not for explicit support podman, but some clean way can bypass this issue"?

          Mark Waite added a comment -

          Based on the docker workflow plugin page, the plugin is up for adoption. Existing maintainers are looking for others who can take responsibility for the plugin. If you'd like to propose a pull request that begins the process of adding podman support, that would be a start to adopting the plugin.

          Mark Waite added a comment - Based on the docker workflow plugin page , the plugin is up for adoption. Existing maintainers are looking for others who can take responsibility for the plugin. If you'd like to propose a pull request that begins the process of adding podman support, that would be a start to adopting the plugin .

            Unassigned Unassigned
            lvronghai ronghai
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: