-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker information not complete #2
Comments
Both arguments should work the same way. Could you please explain what is not clear? |
docker build -f csDockerfile new so I presumed relative path is ok, that is wrong? |
what does path to context mean, what is it supposed to be? |
Ok sudo docker -f csDockerfile context context is a subdirectory!!!! |
It seems to have run without mayor problem, however I don't see any change in the repository. hg (I use mercurial) status does not return any new or changed file. |
Once you create a docker image with csDockerfile, you should have the ability to import all the dependencies (needed for the Python routines) without explicitly installing them. Here you can find the info about how dockerfiles work: https://docs.docker.com/engine/reference/builder/ |
but as I said I run the command as indicated, it did a lot of things and then the repository did NOT change. |
the documentation states
docker build -f (path to csDockerfile) (path to context)
while the first argument seems clear, the second is not.
Please clarify
The text was updated successfully, but these errors were encountered: