delbert_friesen
05/20/2022, 2:13 PMdelbert_friesen
05/20/2022, 2:14 PMmeltano add files docker
the docker file itself uses the working directory projectatharh
05/24/2022, 9:00 PM$(pwd)
) as /projects
in the Docker container, and then setting the same /projects
as the working directory. In the second example, it’s /project
instead. Since we start a new container with each docker run
command, it doesn’t really matter if we use /projects
or /project
. We just need to make sure that the directory names match in the docker run
command.
Another point, if I add the docker file withThis depends on which Docker container you are running this command in. If you are running this command in the container that was started using the second command which usesthe docker file itself uses the working directory projectmeltano add files docker
/project
as the working directory, then that’s the directory that will be used.atharh
05/24/2022, 9:10 PMThis is something we should fix in our docs, but it’s not going to be a problem.Looking at this again, in the first command, we are creating a new Meltano project inside our “projects” directory. It’s then semantically reasonable that we mount the directory as
/projects
. However, the second command is being executed from within the newly created Meltano project directory, that’s why that directory is mounted as /project
. Just good naming practices I think. We second command can also be written as below to be slightly more clear:
docker run -v "$(pwd)":/yourprojectname -w /yourprojectname -p 5000:5000 meltano/meltano