Fails to deploy due to templating error #3

Open
opened 2026-04-16 11:18:26 +00:00 by ryzokuken · 2 comments

Deploying the app fails on current abra versions with FATA <app/deploy.go:276> failed to create miniflux_app: Error response from daemon: rpc error: code = InvalidArgument desc = expanding env failed: expanding env "ADMIN_PASSWORD={{ secret \"admin_password\" }}": template: expansion:1: function "secret" not defined.

My understanding is that probably the template syntax is outdated and we need to fix that on this recipe.

Deploying the app fails on current `abra` versions with `FATA <app/deploy.go:276> failed to create miniflux_app: Error response from daemon: rpc error: code = InvalidArgument desc = expanding env failed: expanding env "ADMIN_PASSWORD={{ secret \"admin_password\" }}": template: expansion:1: function "secret" not defined`. My understanding is that probably the template syntax is outdated and we need to fix that on this recipe.
Author

According to what I could read on https://docs.coopcloud.tech/maintainers/handbook/#manage-secret-data, the syntax is terribly outdated in this repo and we need to fix that in order to make this recipe work.

According to what I could read on https://docs.coopcloud.tech/maintainers/handbook/#manage-secret-data, the syntax is terribly outdated in this repo and we need to fix that in order to make this recipe work.
Author

Hacking on the problem earlier today, I noticed that the issue is isolated to the part of compose.yml which tries to expose all of the data including envvars and secrets to the container by calling

      - DATABASE_URL=postgres://{{ env "DB_USER" }}:{{ secret "db_password" }}@db/{{ env "DB_NAME" }}?sslmode=disable
      - RUN_MIGRATIONS=1
      - ADMIN_USERNAME={{ env "MINIFLUX_ADMIN_USERNAME" }}
      - ADMIN_PASSWORD={{ secret "admin_password" }}
      - BASE_URL=https://{{ env "DOMAIN" }}

which definitely doesn't work but I cannot spend much time figuring out how to fix that atm.

Hacking on the problem earlier today, I noticed that the issue is isolated to the part of `compose.yml` which tries to expose all of the data including envvars and secrets to the container by calling ```yml - DATABASE_URL=postgres://{{ env "DB_USER" }}:{{ secret "db_password" }}@db/{{ env "DB_NAME" }}?sslmode=disable - RUN_MIGRATIONS=1 - ADMIN_USERNAME={{ env "MINIFLUX_ADMIN_USERNAME" }} - ADMIN_PASSWORD={{ secret "admin_password" }} - BASE_URL=https://{{ env "DOMAIN" }} ``` which definitely doesn't work but I cannot spend much time figuring out how to fix that atm.
Sign in to join this conversation.
No description provided.