Use updated docker images #10
Loading…
Reference in New Issue
No description provided.
Delete Branch "change/use-new-docker-images"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have a reworked Karrot release process now ( https://docs.karrot.world/dev/deployment/releases) which results in new releases being publlished over at https://codeberg.org/karrot/karrot/releases.
It builds the docker images, so we can use the same docker images in many contexts. Frontend and backend repos now have unified version numbers.
It's a big change for the images, but should be no user facing changes.
It also moves the geoip out to a separate compose file and container (we can reuse the upstream maxmind one, which can handle all the updating itself).
The new frontend docker image uses the nginx image templating, so we don't need the docker config any more.
The new backend docker image has an entrypoint that directly calls the karrot.cli python module.
Breaking change: now the backend runs as a non-root user, the files have the wrong ownership. This needs a manual step to chown them:
Going to merge right away, as I can't properly try it out until it's on main branch it seems.