[JIRA] (JENKINS-54296) Docker cannot be used right after agent provisioning without sudo

batmat@batmat.net (JIRA)

unread,

Oct 28, 2018, 5:03:02 PM10/28/18

to jenkinsc...@googlegroups.com

Baptiste Mathus assigned an issue to Baptiste Mathus

Jenkins /

JENKINS-54296

Docker cannot be used right after agent provisioning without sudo

Change By:	Baptiste Mathus
Assignee:	R. Tyler Croy Baptiste Mathus

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

batmat@batmat.net (JIRA)

unread,

Oct 28, 2018, 5:03:03 PM10/28/18

to jenkinsc...@googlegroups.com

Baptiste Mathus created an issue

Jenkins /

JENKINS-54296

Docker cannot be used right after agent provisioning without sudo

Issue Type:	Bug
Assignee:	R. Tyler Croy
Components:	evergreen
Created:	2018-10-28 21:02
Labels:	evergreen docker
Priority:	Major
Reporter:	Baptiste Mathus

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)