-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
OCP environment(Red Hat OpenShift Container Platform)
Hello,
The problem is similar as described in podman top -eo failed with error · Issue #8033 · containers/podman (github.com).
We are using docker-pipeline walkflow plugin, the plugin code https://github.com/jenkinsci/docker-workflow-plugin/blob/c7dedefcf68f6ce1320c8aaaeb831628ea21a086/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java#L150 .
Seems still not working for the OCP environment.
[JENKINS-70516] docker-work-flow-plugin failed with Podman will fail when "podman top -eo pid, comm",
ronghai
created issue -
ronghai
made changes -
| Description |
Original:
Hello,
The problem is similar as discribed in [podman top -eo failed with error · Issue #8033 · containers/podman (github.com).|https://github.com/containers/podman/issues/8033] We are using docker-pipeline walkflow plugin, the plugin code [https://github.com/jenkinsci/docker-workflow-plugin/blob/c7dedefcf68f6ce1320c8aaaeb831628ea21a086/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java#L150] . seems still not working for the OCP environment. |
New:
Hello,
The problem is similar as described in [podman top -eo failed with error · Issue #8033 · containers/podman (github.com).|https://github.com/containers/podman/issues/8033] We are using docker-pipeline walkflow plugin, the plugin code [https://github.com/jenkinsci/docker-workflow-plugin/blob/c7dedefcf68f6ce1320c8aaaeb831628ea21a086/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java#L150] . Seems still not working for the OCP environment. |
| Assignee | Original: Viktor Farcic [ vfarcic ] |
| Component/s | New: docker-workflow-plugin [ 20625 ] | |
| Component/s | Original: docker-flow-plugin [ 21438 ] |
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"? 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.
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.