Head slap.... I completely forgot I could do that, thanks for reminding Pierce (its almost better as well, as you can build your image, save it, then run tests on it, and then if it passes all your stages you can included the saved version in your docker build... which sits better with me as it also means that log artifacts etc can be more easily examined for failures (and your not trying to console into a docker image to figure it out). As a nice side effect - if you are doing this in something like Gitlab - you have your project source already there and so you can avoid an extra checkout step, so its a little bit faster.
Pierce - who/where are you rnning your Docker image? Do you use a particular service (or are you running your own?) Tim On Thu, 8 Apr 2021, at 4:29 AM, Pierce Ng wrote: > On Wed, Apr 07, 2021 at 02:21:14AM +0100, Tim Mackinnon wrote: > > I also feel its quite important to call out that the "eval 'Metacello > > new..." command referenced in the DockerFile RUN - is only going to work > > Hi, > > I build my Pharo image outside of Docker. My Dockerfile then packages the > built image plus whatever artefacts required into a Docker image. I am > using my Alpine Linux-based VM. > > GH: https://github.com/pharo-contributions/Docker-Alpine/ > DH: https://hub.docker.com/r/pierceng/pharovm-alpine > > Pierce >
