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

No network connectivity in build containers #11

Open
esben opened this issue Aug 25, 2016 · 1 comment
Open

No network connectivity in build containers #11

esben opened this issue Aug 25, 2016 · 1 comment

Comments

@esben
Copy link
Member

esben commented Aug 25, 2016

By running all build steps in Docker containers without network connectivity, problems with build reproducability caused by non-reproducable network communication is removed.

Fetching of source code and other build step inputs must of-course then be handled in another way.

@esben
Copy link
Member Author

esben commented Aug 25, 2016

Maybe adopt a similar approach as Baserock (http://www.baserock.org), where all fetching is done using git. Anything that is in git upstream, is then mirrored to a git repository (using Trove).

With this approach, we could streamline fetching and signature handling much more, as we are only fetching from git. And with fetching being much simpler, it becomes more realistic to do a clean integration that is not running inside build containers.

Further, by doing this, the problem of sharing fetch caches goes away. There will be only 1 fetcher, and all build steps simply get the sources added to the container before start.

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

1 participant