Conversation
|
|
|
I guess we could disable pulls via some option. I haven't really understood this myself, but as you said an image that depends on a locally built image won't need to pull. But I guess that is only true if the "base image" inside the repository specifies a strict version (like node:6.8.0 for example). |
6a5a570 to
21186c3
Compare
|
Rebased, previous was 6a5a570 |
|
Had another case of this now, with a test container doing Didn't work with the regular build-contract image, but with |
|
Reminder: this issue is a major gotcha. I just got an old build from a new git commit, thanks to docker cache on the build node. Turns out I was using Will change to |
into avoid-pull-for-local-dependency
21186c3 to
9a2a394
Compare
with localhost:5000/... image names if you forget the PUSH_TAG so let's have it in the example even if some builds don't use it
|
I've rebased and built Also included a commit that was quite essential for #36. @atamon We should use this build all over the place, and merge if not a lot breaks. That'll give us a single build-contract image to keep track of. I've forgotten if there were any downside with d2a9cb1 or not. |
requiring us to use images tagged with sha, which is a requirement anyway for builds to be stable over time. If we really want pull on every build we must find a docker-compose feature akin to imagePullPolicy in k8s
|
docker/compose#3574 (comment) suggests what I was looking for and docker/compose#3574 (comment) and refereces the kubernetes solution like I did in 6671feb. I've built Will make another build on monday with latest nodejs and npm because fixes in https://github.com/npm/npm/releases/tag/v6.1.0 may apply to our monorepo solution. |
|
Built from master now, with https://github.com/Yolean/docker-base/releases/tag/docker.node.9d02ee07572e98ce3db9018ac6ee2a70b12464498d3ea36aca0e9d6fb660eba7
|
For #12
Or we have to use exact tags/sha256 for all upstream images everywhere.
Building experimental solsson/build-contract-push from this branch.