Was this the right way to build the image?

[Marxsal]

There weren't any instructions how we were supposed to build the docker image, so I improvised as best I could. Maybe someone else will find the following helpful, or maybe someone can point out what I should have done differently.

---

Node and NPM were already installed.

I used git to clone pigallery2:

git clone https://github.com/bpatrik/pigallery2.git

Made source code changes where needed.

Then in root of project, ran

npm install

and then

npm run create-release -- --languages=nl

This creates a file, pigallery2.zip. It lists about 70 potential problems with the node files, some claiming to be critical. Since this will be running in docker, behind a reverse proxy, I hope those don't matter too much.

Then I moved the pigallery2.zip file into ./docker/alpine.

I unzipped the pigallery2.zip file and renamed the resulting directory pigallery2-release

I did a few things and then discovered that I needed to edit Dockerfile.build. I commented out the places where it wants to delete the cache:

# /var/cache/apk/

Then I ran:

docker build -f Dockerfile.build -t marxsal/pigallery2:alpine

Now I was able to go where my pigallery2 docker compose file lives, change the image to marxsal/pigallery2:alpine, and then run docker compose the usual way

Since this is not the target platform, I saved the docker image:

docker save -o pigallery.tar marxsal/pigallery2:alpine

Note that it is important to identify the image by its tag so that it will arrive at its destination with the same tag.

I loaded it up to the actual platform and loaded it into docker:

docker load -i pigallery.tar

[kagahd]

There weren't any instructions how we were supposed to build the docker image,

I think the best "documentation" about building docker images is the github workflow which builds the images. See https://github.com/bpatrik/pigallery2/blob/master/.github/workflows/build.yml

However, there were a few glitches that PR #1000 solves.

[Marxsal]

As an instructional aid, it's somewhat lacking in that it makes calls to actions that aren't part of the script. But it appears I did basically the same thing it did, but I could have had fewer warning messages if I had used particular options.

Thanks!