Lucas RayanandClaude Opus 5
13fd2a9cee
The deployment failed on the migrate service. Coolify rewrites a relative bind mount to a path under its own application directory, and when that resolves to an empty directory golang-migrate finds no migrations and exits 1 - with nothing useful in the deployment log to say why. A deployment that pulls its images has no business also depending on files being at a particular path on the host. Both mounts are now baked into images built from the repository root: migrations - the schema, so migrate always has it rspamd - actions.conf and ratelimit.conf The Rspamd one mattered for a quieter reason: Rspamd starts happily with an empty local.d, so a mount that resolved to nothing would have left the rate limits and score thresholds unapplied. The defence would have looked configured and done nothing. Both images join the CI and release matrices, building from the root context. Verified by building them, checking their contents, and bringing the whole stack up - Rspamd reports its nine rate directives loaded from the image. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
14 lines
517 B
Docker
14 lines
517 B
Docker
# The migrations travel inside an image rather than a bind mount.
|
|
#
|
|
# A deployment that pulls its images has no reason to also depend on files
|
|
# being present at a particular path on the host: the orchestrator rewrites
|
|
# relative bind mounts to its own layout, and an empty directory silently
|
|
# becomes "no migrations found" - which fails the deploy with no useful error.
|
|
#
|
|
# Build context is the repository root.
|
|
FROM migrate/migrate:v4.17.1
|
|
|
|
COPY migrations /migrations
|
|
|
|
ENTRYPOINT ["migrate", "-path=/migrations"]
|