Repository navigation
Release 1.11.0
Goiabada 1.11.0
Smaller images built from an empty base, which check their own health, and a check-authserver command for an admin console that can't reach the auth server. All changes
Before upgrading
- #808 If you upgrade a Docker Compose deployment without rerunning the setup wizard, such as one with no
goiabada-setup.yaml(set up before 1.9.0) or one whose image lines you change yourself: when you set both image lines to 1.11.0, also change the auth server'shealthchecktestto["CMD", "/app/goiabada-authserver", "healthcheck"], since the images hold nowget. Rerunning the setup wizard overgoiabada-setup.yaml, as Upgrade Goiabada shows, does this for you. With the old check, the auth server keeps serving, but Docker Compose reports it unhealthy and doesn't start the admin console.
Upgrade notes
- #808 If a health check, script,
execorkubectl cpof yours runswget,sh,taror another program inside a Goiabada container: the images hold only the server now. Use itshealthcheckcommand, or a tool container beside it, as Debugging without a shell shows with Docker Compose and on Kubernetes. A KuberneteshttpGetprobe on/health, as the wizard's manifest has, needs no change. - #808 If you set a server's listener host or port with flags and run its image with no health check of your own, as a plain
docker runor a Docker Swarm service: set the listener in the container's environment too. The image's check reads only the environment, so it asks the default listener, and Swarm replaces a container it reports unhealthy. - #808 If you roll back to an earlier release without its setup wizard: put the auth server's
wgethealth check back, since earlier releases have nohealthcheckcommand. - #808 If a Dockerfile of yours builds
FROM leodip/goiabada:…and runsRUNin that stage: do that work in an earlier stage built from another image, andCOPYthe result in. A program you copy in must be statically linked. - #808 If a Dockerfile of yours adds a certificate authority to the image's bundle in a
RUN: mount its certificate and pointSSL_CERT_FILEat it instead, as What the images contain shows. - #808 If you scripted the SQLite restore or the ownership fix from the 1.10 docs, which run
docker compose run --entrypoint shor--entrypoint chown: run them from a BusyBox container that takes the service's volumes, as Database and attempt to write a readonly database now show. - #808 If you run a Goiabada image as the user
goiabadaby name: use10001:10001, since the images have no/etc/passwd.
⚙️ Config changes
- Database: no migrations; the schema stays at
000088on SQLite, MySQL, PostgreSQL and SQL Server. - #808 Both images are built from an empty base. Each holds its server's binary, the CA bundle at
/etc/ssl/certs/ca-certificates.crtand/tmp, and the auth server's adds/dataand/bootstrap. Both still run as10001:10001. - #808 Each image declares its own health check,
/app/goiabada-<server> healthcheckevery 10 seconds, with a 5-second timeout, 3 retries and a 5-minute start period. Under Docker, it applies wherever nothing sets one: a plaindocker run, a Docker Swarm service, and the admin console under the wizard's Compose file. - #808 The setup wizard's Compose file checks the auth server with
["CMD", "/app/goiabada-authserver", "healthcheck"].
New
- #808
goiabada-authserver healthcheckandgoiabada-adminconsole healthcheckcheck their server's own/health, exiting0when it answers200, for a Compose file or an orchestrator of your own. - #808
goiabada-adminconsole check-authservermakes the admin console's settings call to the auth server once and prints what it met. Can't reach the auth server runs it on Docker Compose, Kubernetes and native installs.
Fixed
- #808 The admin console refuses a word on its command line that names no command, with exit
2and a line naming the word, instead of ignoring it and every flag after it.
Maintenance
- #808 CI builds both images for
linux/amd64andlinux/arm64, cross-compiled, and scans the server binary in each with govulncheck before a release publishes anything. - #808 The weekly image scan reports a Go finding as a vulnerable symbol detected in the binary, which doesn't prove the code reaches it.
- Docs: claims the code contradicts are corrected, and text readers don't need is cut.
Pinned image references
The multi-platform image index digests this release pushed and attested, one per image. The same digests name the images at ghcr.io/leodip/goiabada, which the same push wrote.
- Auth server:
leodip/goiabada:authserver-1.11.0@sha256:25719d38ce8898c811b02eb0659747a5c9efeac201d835e213aec30dd858c577 - Admin console:
leodip/goiabada:adminconsole-1.11.0@sha256:f3e612661fd730eafdf8d08a8a1009c41d528a70c4d688cf01384a40b359ebdb