poorejc commented on issue #42:
URL: 
https://github.com/apache/incubator-flagon-useralejs/issues/42#issuecomment-793277041


   @snehalghute sorry you're running into trouble.
   
   I tore my entire build down and rebuilt from scratch without 
error--unfortunately, I can't replicate the error going through our 
instructions at https://github.com/apache/incubator-flagon/tree/master/docker
   
   I do notice from your error message that you are mounting volumes from 
"/d/Work/incubator-flagon-master/docker/logstash/6.8.2/pipeline/logstash-userale.conf\"
 on a linux box. If you're running Mac or linux you have to mount volumes from 
a a shared directory. By default these are: /Users, /Volume, /private, /tmp and 
/var/folders
   
   from https://docs.docker.com/docker-for-mac/
   
   "FILE SHARING
   Use File sharing to allow local directories on the Mac to be shared with 
Linux containers. This is especially useful for editing source code in an IDE 
on the host while running and testing the code in a container. By default the 
/Users, /Volume, /private, /tmp and /var/folders directory are shared. If your 
project is outside this directory then it must be added to the list. Otherwise 
you may get Mounts denied or cannot start service errors at runtime."
   
   I suggest that you either:
   
   1. clone https://github.com/apache/incubator-flagon/tree/master/docker to a 
directory in the path of one of the shared dirs above and then try again (I 
just successfully build our distro from a sub dir in my /user dir).
   2. follow the directions under "File Sharing" to add your /d/Work/... dir to 
the list of shared dirs and then try again.
   
   Hopefully, that clears things up. If not we can keep troubleshooting.
   
   It would also be helpful to get the version of Docker Engine and Compose you 
are running on.
   
   Good luck!
   
   


----------------------------------------------------------------
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]


Reply via email to