-
Notifications
You must be signed in to change notification settings - Fork 7
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 runtime follow up #234
Conversation
186d74d
to
b9b3d2f
Compare
Currently the CI job itself is flaky with some permission problems. I will investigate that one further but in the meantime the PR can be reviewed. |
ff3b196
to
b15bac4
Compare
We need to override the docker image with the tag from the current branch. |
09716ae
to
e548b5d
Compare
f793c8c
to
5be5dc3
Compare
5dbd0d2
to
8defd7e
Compare
@bauersimon docker test runs through. Please review all again did some major reworking. |
because the paths of the host and inside the container might differ.
8fad6c9
to
a1ad3a9
Compare
By using a MultiStage build we avoid copying the whole evaluation repository into the Docker image. Also fixed some creations of folders and permissions regarding non-docker run containers.
14ed973
to
7d2b8f6
Compare
7d2b8f6
to
ddd1e54
Compare
I had to skip the docker runtime in local tests for now as we do have a problem with the "commit hashes" - I hope we can fix that with: #207 Docker runtime tests are skipped locally and only run inside the Github Actions CI |
No description provided.