Skip to content
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

Open
ouboub opened this issue Sep 16, 2021 · 7 comments
Open

docker information not complete #2

ouboub opened this issue Sep 16, 2021 · 7 comments

Comments

@ouboub
Copy link
Contributor

ouboub commented Sep 16, 2021

the documentation states
docker build -f (path to csDockerfile) (path to context)

while the first argument seems clear, the second is not.
Please clarify

@fragut01
Copy link
Owner

Both arguments should work the same way. Could you please explain what is not clear?

@ouboub
Copy link
Contributor Author

ouboub commented Sep 16, 2021

Both arguments should work the same way. Could you please explain what is not clear?

docker build -f csDockerfile new
unable to prepare context: path "new" not found

so I presumed relative path is ok, that is wrong?

@ouboub
Copy link
Contributor Author

ouboub commented Sep 16, 2021

Both arguments should work the same way. Could you please explain what is not clear?

what does path to context mean, what is it supposed to be?

@ouboub
Copy link
Contributor Author

ouboub commented Sep 17, 2021

Ok
the syntax should be in the main directory:

sudo docker -f csDockerfile context

context is a subdirectory!!!!
however that starts to install pkg from Ubuntu 18.04 and I am running Ubuntu 16.04, I hope that does not damage
my system.
Sorry, but the information/manual provided so far has not sufficiently be tested.

@ouboub
Copy link
Contributor Author

ouboub commented Sep 17, 2021

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.
Please clarify

@fragut01
Copy link
Owner

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/

@ouboub
Copy link
Contributor Author

ouboub commented Sep 17, 2021

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.
where is the generated file and what is its purpose.
I don't want to read a documentation, I would like to have some short explanations,
shall I mount this image, where is the image etc etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants