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

Docker cannot be used right after agent provisioning without sudo

    XMLWordPrintable

    Details

    • Sprint:
      Evergreen - Milestone 2
    • Similar Issues:

      Description

      Problem statement

      Though the user is configured to have the necessary permissions to not require sudo to use docker, it does not work.

      The workaround is to manually disconnect, then reconnect the agent. This is because the script is run in the connecting session, then no logout/login is performed.

      Expected behavior

      docker should be usable right away after agent provisioning.

      Though we could require users to use sudo, this is likely a major hurdle since users (like evergreen codebase) itself will probably have scripts that run docker without sudo (and as a simple alias won't be enough, then we'd move more and more away from keeping Evergreen simple to use)

        Attachments

          Activity

          Hide
          imod Dominik Bartholdi added a comment -

          I worked around this by setting up my own AMI where docker is already installed

          Show
          imod Dominik Bartholdi added a comment - I worked around this by setting up my own AMI where docker is already installed

            People

            • Assignee:
              batmat Baptiste Mathus
              Reporter:
              batmat Baptiste Mathus
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: