autonomic-bot
1a098452f4
Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT secret to /etc/gitea/app.ini at LoadCommonSettings. With app.ini mounted directly as a read-only swarm config this fails fatally (open /etc/gitea/app.ini: read-only file system) on a warm reattach/redeploy, crash-looping the container before any DB migration. Mount the rendered config at /etc/gitea/app.ini.init (read-only) and seed it once into the writable config volume via docker-setup.sh, so Gitea owns a writable /etc/gitea/app.ini. Bumps DOCKER_SETUP_SH_VERSION so the new entrypoint actually deploys.
27 lines
1.3 KiB
Cheetah
27 lines
1.3 KiB
Cheetah
#!/bin/bash
|
|
|
|
# modified version of https://github.com/go-gitea/gitea/blob/d7dbe4feebac7805a4ca184f0989f58de8063d96/docker/rootless/usr/local/bin/docker-setup.sh
|
|
# also see https://github.com/go-gitea/gitea/pull/14762#issuecomment-829224656
|
|
|
|
# Prepare git folder
|
|
mkdir -p ${HOME} && chmod 0700 ${HOME}
|
|
if [ ! -w ${HOME} ]; then echo "${HOME} is not writable"; exit 1; fi
|
|
|
|
# Prepare custom folder
|
|
mkdir -p ${GITEA_CUSTOM} && chmod 0500 ${GITEA_CUSTOM}
|
|
|
|
# Prepare temp folder
|
|
mkdir -p ${GITEA_TEMP} && chmod 0700 ${GITEA_TEMP}
|
|
if [ ! -w ${GITEA_TEMP} ]; then echo "${GITEA_TEMP} is not writable"; exit 1; fi
|
|
|
|
# Seed app.ini into the WRITABLE config volume (/etc/gitea) from the read-only swarm config
|
|
# (mounted at /etc/gitea/app.ini.init). Gitea must be able to PERSIST settings to app.ini — e.g.
|
|
# Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT_SECRET at LoadCommonSettings; with app.ini
|
|
# mounted directly as a read-only swarm config this fails fatally ("open /etc/gitea/app.ini:
|
|
# read-only file system") on (re)deploy. Seed-once preserves any runtime-persisted state across
|
|
# restarts/upgrades; delete /etc/gitea/app.ini to re-seed from the recipe's rendered config.
|
|
if [ ! -f /etc/gitea/app.ini ]; then
|
|
cp /etc/gitea/app.ini.init /etc/gitea/app.ini
|
|
fi
|
|
chmod 0600 /etc/gitea/app.ini 2>/dev/null || true
|