hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1518) Use /etc/ozone for configuration inside docker-compose
Date Mon, 13 May 2019 15:53:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1518?focusedWorklogId=241140&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241140

ASF GitHub Bot logged work on HDDS-1518:

                Author: ASF GitHub Bot
            Created on: 13/May/19 15:52
            Start Date: 13/May/19 15:52
    Worklog Time Spent: 10m 
      Work Description: anuengineer commented on pull request #814: HDDS-1518. Use /etc/ozone
for configuration inside docker-compose 
URL: https://github.com/apache/hadoop/pull/814#discussion_r283415507

 File path: Dockerfile
 @@ -36,7 +36,9 @@ RUN chown hadoop /opt
 ADD scripts /opt/
 ADD scripts/krb5.conf /etc/
 RUN yum install -y krb5-workstation
+RUN mkdir -p /etc/hadoop && mkdir -p /var/log/hadoop && chmod 777 /etc/hadoop
&& chmod 777 /var/log/hadoop
+ENV HADOOP_LOG_DIR=/var/log/hadoop
+ENV HADOOP_CONF_DIR=/etc/hadoop
 Review comment:
   Did you want to write /etc/ozone here ?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 241140)
    Time Spent: 0.5h  (was: 20m)

> Use /etc/ozone for configuration inside docker-compose 
> -------------------------------------------------------
>                 Key: HDDS-1518
>                 URL: https://issues.apache.org/jira/browse/HDDS-1518
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> As [~eyang] reported the docker-compose clusters write the config files with uid=1000.
In case of the build is created with different user (eg id=401) the hadoop user inside the
container (id=100) can't work to the ozone/etc/hadoop directory.
> I propose to generate the configuration file to /etc/hadoop (And add that directory to
the classpath). In that case the volume mount of the ozone distribution folder can be read

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message