src-d / infrastructure-dockerfiles

Dockerfile-s to build the images which power source{d}'s computing infrastructure.

source{d} infrastructure Dockerfile-s

Dockerfile-s which are used to build images powering source{d}.

External contributions

Although we don't expect you to add new images unless you are a source{d} employee, we will be grateful for any bug reports or fixes.

License

Apache 2.0, see LICENSE.

infrastructure-dockerfiles's Issues

publish-new.sh does not fail on error

And we cannot notice easily in Travis failed buildss

ml-infra build fails due to HUGE logs

I have noticed that if I update the lowest image in our stack - ml-infra-base-python - the CI build fails due to the log exceeding the maximum length limit.

This is most likely due to building numpy and scipy, which floods the console with verbose compilation commands.

I am not sure what's the best way to solve this problem:

• Silence numpy and scipy
• Invent something else in the CI scripts and avoid this problem once and for all

Provide write access to vmarkovtsev

As discussed with @smola I should have the ability to merge Dockerfile PRs to ml-infra-* myself.

Add hadolint-ing the Dockerfile-s

@mcuadros used https://github.com/hadolint/hadolint for the docker best practices dashboard in sourced-ee. It found sensible problems in our own Dockerfiles according to @warenlg
Let's add it to our CI?

Hue fails to build in Travis

After a while, build gets stalled and fails with this message

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated

publish-new.sh fails to get executed

https://travis-ci.com/src-d/infrastructure-dockerfiles/builds/111066316

0.01s$ ./scripts/publish-new.sh
The command "./scripts/publish-new.sh" exited with 1.

cc @meyskens