custom/conf/app.ini ignored while starting Docker container #1021

New Issue

GiteaMirror · 2025-11-02T03:45:31-06:00

GiteaMirror commented

2025-11-02 03:45:31 -06:00

Originally created by @liquidat on GitHub (Aug 30, 2017).

Gitea version (or commit ref): docker.io/gitea/gitea:latest, e0b191e68268
Git version: see above
Operating system: see above
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

When the container is started with a custom app.ini at /data/gitea/custom/conf/app.ini as described in tihe configuration cheat sheet , the values in this file are ignored. Most notably, the installer is launched although INSTALL_LOCK is set to true.

In issue #2173 it is mentioned that the custom file might not be read due to a different default gitea path. However, as mentioned above the custom path is properly mounted to the correct container path.

When the custom app.ini is not written to /data/gitea/custom/conf/app.ini but instead written to /data/gitea/conf/app.ini, everything works as expected and the installer is not used. However, this solution is not feasable because that way the app.ini is altered afterwards and cannot be properly monitored for changes with config management tools.

Originally created by @liquidat on GitHub (Aug 30, 2017). - Gitea version (or commit ref): docker.io/gitea/gitea:latest, e0b191e68268 - Git version: see above - Operating system: see above - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When the container is started with a custom app.ini at `/data/gitea/custom/conf/app.ini` as described in tihe [configuration cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/) , the values in this file are ignored. Most notably, the installer is launched although `INSTALL_LOCK` is set to true. In issue #2173 it is mentioned that the custom file might not be read due to a different default gitea path. However, as mentioned above the `custom` path is properly mounted to the correct container path. When the custom `app.ini` is not written to `/data/gitea/custom/conf/app.ini` but instead written to `/data/gitea/conf/app.ini`, everything works as expected and the installer is not used. However, this solution is not feasable because that way the app.ini is altered afterwards and cannot be properly monitored for changes with config management tools.

GiteaMirror added the type/question label 2025-11-02 03:45:31 -06:00

GiteaMirror closed this issue

2025-11-02 03:45:31 -06:00

GiteaMirror commented

2025-11-02 03:45:31 -06:00

@liquidat commented on GitHub (Jun 7, 2018):

Closing, since the container customization has changed since this issue was opened.

@liquidat commented on GitHub (Jun 7, 2018): Closing, since the container customization has changed since this issue was opened.

GiteaMirror referenced this issue

2025-11-02 11:52:55 -06:00

[PR #1021] [MERGED] Added missing new struct sync #15714

Sign in to join this conversation.