Build using custom/local Docker registry #65
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft (at least) until:
The tweak to
opam init
can obviously be spun out to another PR, as can the--submission-service
change.I've started updating
README.md
with instructions on running a local scheduler and worker and also a local development docker registry, so on my machine I can saydocker run --rm -it localhost:5000/ocurrent/opam
. This could be updated to do similarly for the reads, and make it entirely free of Docker Hub... but the main reason I hacked this in originally was because I being lazy about having to set-up the secrets on my Docker ID 🙂