Description
Prerequiste
Cookieplone Questions answered with defaults to use all the bells and whistles
[15/17] Should we setup a caching server?
1 - Yes
2 - No
Choose from [1/2] (1):
[16/17] Add Ansible playbooks?
1 - Yes
2 - No
Choose from [1/2] (1):
[17/17] Add GitHub Action to Deploy this project?
1 - Yes
2 - No
Choose from [1/2] (1): Failure to build images
While CI actions succed to build custom images for the project for the linux/amd64 platform
only the external images for traefik, postgres and recently cluster-purger are available for linux/arm64
The Manual deployment seem to work first but the containers cannot be created due to the lacking custom images for backend, frontend, varnish.
Together with @pbauer we fixed that during the sprint.
For the GitHub - kitconcept/cluster-purger: Purge multiple instances of Varnish inside a cluster pbauer managed to get a arm package build as PR with support by kitconcept closing my ticket
There is now a 3rd image for linux/arm64 available under the top tab OS / Arch.
But this is not yet reflected in the Cookieplone-template created workflows yet.
The solution is to replace platforms: linux/amd64 with platforms: linux/amd64,linux/arm64 in backend.yml, frontend.yml and varnish.yml.
I am currently building all 3 including arm successfully...
frontend image build process very slow
The frontend image build process is now very slow and extends to over 40 minutes for all platforms.
Therefore people only in need for intel, have to wait for their individual images far too long to complete the whole workflow successfully.
It therefore makes sense to consider configuring the actions via an .env variable and, if necessary, to query them in the cookie cutter and tell it where to simply change them later:
build_platforms= ["linux/amd64", "linux/arm64"]
Currently the Manual deployment is still not running through smooth and hangs with the frontend containers starting over again and again.
corepack issue
There is also a temporary fix for the corepack issue mentioned in the community post that may has conflicting effects
Currently you need to tweak the frontend workflow to work around a corepack issue (see topic: corepack problems (specially in CI)) but it generally works building the images.
PR postponed.
Adding the extended platform code in the workflows is easy. But I postpone a pull request because of the slowing down effect until I have a proper idea how to manage that. Until then it could be an experimental branch.