archive snowblossom slack dev
prev 2020-12-04 next
2020-12-04 08:30:26
Rotonen
for the sake of learning: what was the issue with the dockerfile?
2020-12-04 11:10:14
Rotonen
curiously many builds
2020-12-04 17:35:01
Fireduck
I suspect it was catching up somehow. Those bazel builds start from nothing and download a lot of things. They work great on a machine where the cache gets populated, not so great on docker.
2020-12-04 17:36:38
Fireduck
Mostly a conflict in that the rosetta api expectations want a docker file that doesn't do any COPY and gets stuff from a git repo based on a tag. Where as I want to have the latest git commit built to latest. That can probably be done with the same file if I could have dockerhub pass in the commit number as the refspec but I'm not sure.
2020-12-04 17:45:23
Fireduck
I'm considering adding a layer that just builds a release of snowblossom to bring in most of the bazel cache needs.
2020-12-04 17:52:32
Rotonen
that would work
2020-12-04 17:52:58
Rotonen
i thought i avoided COPY, what was still copied in?
2020-12-04 17:53:02
Rotonen
or even cross-stage copy?
2020-12-04 17:55:15
Fireduck
You did it right, I just wanted a separate one that does do it via a copy
2020-12-04 17:55:38
Fireduck
At least until I figure out how to have dockerhub pass in the commit sha1
2020-12-04 17:55:49
Fireduck
For building :latest
2020-12-04 17:55:53
Rotonen
well, you could just use mine and pass the refspec in
2020-12-04 21:02:25
Clueless
dockerhub supports linking as well. These might be a result of upstream changes.