mattmassicotte opened a new issue #11278:
URL: https://github.com/apache/druid/issues/11278


   ### Affected Version
   0.21.1-rc1
   
   ### Description
   
   So far, I've never been able to use AWS Fargate bind mounts (ie Docker 
volumes) with Druid. I have a workaround of using EFS mounts, but it is a real 
pain to use. I was really excited to see that 0.21.1-rc1 included a change to 
the Dockefile, so I decided to check it out. Unfortunately, it still does not 
work.
   
   The druid process fails to start with the following logging:
   
   ```
   mkdir: can't create directory 'var/tmp': Permission denied
   mkdir: can't create directory 'var/druid/': Permission denied
   mkdir: can't create directory 'var/druid/': Permission denied
   mkdir: can't create directory 'var/druid/': Permission denied
   mkdir: can't create directory 'var/druid/': Permission denied
   mkdir: can't create directory 'var/druid/': Permission denied
   ```
   
   I'm neither a Fargate, Druid, or Docker expert. But, from what I can gather, 
Fargate is very sensitive to the nature of the path in the `VOLUME` command in 
the Dockerfile.
   
   Some details here:
   
   https://github.com/aws/containers-roadmap/issues/938#issuecomment-812590686
   
   An AWS employee actually looked the the Druid Dockefile and identified the 
symlinking as the issue. I figured I'd open this bug since it is indeed still 
not quite compatible with Fargate and this area was just touched.
   
   If I can help in some way, I'd really love to, as this is currently 
affecting my ability to easily scale Druid. Each new instance requires a 
special EFS mount point, which it turn requires a special ECS task definition. 
Regular docker volume support would be awesome.


-- 
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to