-
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 image does not build #44
Comments
@dgarijo It is unfortunate that OEG's Software Catalog Creator (scc) has the same name as https://pypi.org/project/scc/ |
Is 820c86c a fix for this issue? I am able to build a container image with this commit. |
It is unusual that the first step of the Dockerfile is to do a Concretely, it unfortunately breaks any fork of the project, since the container image is always built from the original repository, rather than from the code in the fork. |
@davidjsherman, I just realized on the clash of names. We will probably change it since it's on its early stages. |
If you are using Docker to build the container image, you can specify a Git repository instead of a directory; Docker will do a clone to get its build context: % docker build -t ya2ro:latest 'https://github.com/oeg-upm/ya2ro.git#main'
=> [internal] load git source https://github.com/oeg-upm/ya2ro.git#main 1.4s
=> [internal] load metadata for docker.io/library/python:3.9 2.9s
=> [1/4] FROM docker.io/library/python:3.9@sha256:a83c0aa6471527636d7331c30704d0f88e0ab3331bbc460d4ae2e53bbae64 22.6s
... If you build the image as part of a continuous integration, then the CI system will do the So it isn't necessary to explicitly check out the source in the Dockerfile. |
Ah! I did not know this. Thanks a lot!! |
I have tried to build the docker image, but returns in a result.
I thin this is cause by scc not installing properly.
The text was updated successfully, but these errors were encountered: