You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/17 19:56:00 UTC

[jira] [Commented] (AVRO-1946) If user exists by default in docker, there will be an error, and the setup fails.

    [ https://issues.apache.org/jira/browse/AVRO-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745439#comment-16745439 ] 

ASF subversion and git services commented on AVRO-1946:
-------------------------------------------------------

Commit 0d997e5e5952546e0bdeab3080ef7c00d8caffc1 in avro's branch refs/heads/master from sacharya
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=0d997e5 ]

AVRO-1946 - Continue if user already exists.

Currently, if the user running ./build.sh docker already exists on the docker image then there is an error thrown and it stops.
This is not ideal. So creating it to throw a warning, but still continuing.
This makes it consistent with groupadd.

Signed-off-by: sacharya <su...@gmail.com>


> If user exists by default in docker, there will be an error, and the setup fails.
> ---------------------------------------------------------------------------------
>
>                 Key: AVRO-1946
>                 URL: https://issues.apache.org/jira/browse/AVRO-1946
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 1.9.0
>            Reporter: Suraj Acharya
>            Assignee: Suraj Acharya
>            Priority: Minor
>             Fix For: 1.9.0
>
>         Attachments: AVRO-1946.patch
>
>
> Currently, when a user already exists in a docker, it errors and stops running.
> However, for a group it continues after throwing a warning. This is inconsistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)