You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Yetus QA (JIRA)" <ji...@apache.org> on 2019/02/03 21:21:00 UTC
[jira] [Commented] (YETUS-771) Dockerfile.patchspecific doesn't
work when gid isn't defined
[ https://issues.apache.org/jira/browse/YETUS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759544#comment-16759544 ]
Yetus QA commented on YETUS-771:
--------------------------------
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/931/console in case of problems.
> Dockerfile.patchspecific doesn't work when gid isn't defined
> ------------------------------------------------------------
>
> Key: YETUS-771
> URL: https://issues.apache.org/jira/browse/YETUS-771
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.9.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Minor
> Labels: beginner
> Fix For: 0.10.0
>
> Attachments: YETUS-771.00.patch
>
>
> If test-patch is run on a node without docker installed, this code
> {code}
> RUN if [ "${DOCKER_SOCKET_GID}" = -1 ]; then groupadd --non-unique --gid ${DOCKER_SOCKET_GID} dockersock || true; fi
> {code}
> ... won't work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)