• Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Blocker Blocker
    • docker-workflow-plugin
    • CentOS 7.8 using podman-1.6.4-18.el7_8.x86_64
      Plugin version: Docker Pipeline 1.23

      Hi developers,

      we use podman with the docker emulation instant of native docker.

      The pull of the image works, but the start of the container fails with:

       Posting build status of FAILED to Git for commit id [c0fd73dba1f80622cff871baae31fc04ed6af5b9] and ref 'refs/heads/master'
      ERROR: The docker version is less than v1.7. Pipeline functions requiring 'docker exec' (e.g. 'docker.inside') or SELinux labeling will not work.
      Finished: FAILURE

      But this version contains the needed command:

      docker exec --help
      Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
      Run a process in a running containerDescription:
        Execute the specified command inside a running container.
      Usage:
        podman exec [flags] CONTAINER [COMMAND [ARG...]]Examples:
        podman exec -it ctrID ls
        podman exec -it -w /tmp myCtr pwd
        podman exec --user root ctrID lsFlags:
            --detach-keys string   Override the key sequence for detaching a container. Format is a single character [a-Z] or ctrl-<value> where <value> is one of: a-z, @, ^, [, , or _
        -e, --env stringArray      Set environment variables
        -i, --interactive          Keep STDIN open even if not attached
        -l, --latest               Act on the latest container podman is aware of
            --preserve-fds int     Pass N additional file descriptors to the container
            --privileged           Give the process extended Linux capabilities inside the container.  The default is false
        -t, --tty                  Allocate a pseudo-TTY. The default is false
        -u, --user string          Sets the username or UID used and optionally the groupname or GID for the specified command
        -w, --workdir string       Working directory inside the container
       

          [JENKINS-63233] Unable to use it with podman-docker

          mdc system added a comment -

          I have get running it using this 2 patches. I know it is very dirty, but I think it give you an hint where the problem in the code is.
           

          mdc system added a comment - I have get running it using this 2 patches. I know it is very dirty, but I think it give you an hint where the problem in the code is.  

          Michael Gray added a comment -

          For others trying to adopt podman in Jenkins...  This project: https://github.com/mgoltzsche/jenkins-jnlp-slave offers a slightly "less dirty" workaround in the form of a replacement docker script for podman-docker that reworks some command line options to suit the Jenkins docker plugin.  True podman support in the plugin would be nice, but this script another workaround.

          kudos to https://github.com/mgoltzsche!

          Michael Gray added a comment - For others trying to adopt podman in Jenkins...  This project:  https://github.com/mgoltzsche/jenkins-jnlp-slave  offers a slightly "less dirty" workaround in the form of a replacement docker script for podman-docker that reworks some command line options to suit the Jenkins docker plugin.  True podman support in the plugin would be nice, but this script another workaround. kudos to  https://github.com/mgoltzsche !

          I think this bug may be invalid. This assumes that this plugin should support podman, when it was really written to support Docker. 

          Now, looking at the code and the current version of podman, I'm curious whether this issue is still a thing. AFAIU, the problem was probably that podman version was < 1.7 when this issue got reported. But given nowadays podman version is 4.x, I assume this should not raise an exception anymore for somebody not using and extremely old version of podman from before 2020?

          Baptiste Mathus added a comment - I think this bug may be invalid. This assumes that this plugin should support podman , when it was really written to support Docker.  Now, looking at the code and the current version of podman , I'm curious whether this issue is still a thing. AFAIU, the problem was probably that podman version was < 1.7 when this issue got reported. But given nowadays podman version is 4.x, I assume this should not raise an exception anymore for somebody not using and extremely old version of podman from before 2020 ?

          Carroll Chiou added a comment -

          Closing this ticket as "Won't Do" as this plugin existed before podman. It may also be that this is no longer an issue as the podman version reported in this is quite old. Should this issue need to be revisited, a new feature request should be created.

          Carroll Chiou added a comment - Closing this ticket as "Won't Do" as this plugin existed before podman. It may also be that this is no longer an issue as the podman version reported in this is quite old. Should this issue need to be revisited, a new feature request should be created.

            Unassigned Unassigned
            mdc_system mdc system
            Votes:
            5 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: