My automatic install stopped working #1924

New Issue

GiteaMirror · 2025-11-02T04:17:59-06:00

GiteaMirror commented

2025-11-02 04:17:59 -06:00

Originally created by @w2ak on GitHub (Jun 12, 2018).

Gitea version (or commit ref): docker hub's gitea:latest
Operating system: docker in Ubuntu 16.04
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

So I've been using ansible to automatically install and configure Gitea. I build my own docker image from gitea and have an entrypoint that creates the admin if necessary.

As you can see in my docker-compose file, the INSTALL_LOCK variable is always set to true.

However, I end up on the Gitea install web page.

As you can see in my Dockerfile, I only append app_custom.ini to the original default template. This was working before (around may 30 according to my git log).

However, after starting the container, the configuration file only contains the INTERNAL_KEY.

Finally, here is my docker-entrypoint.sh. I haven't changed it since the time it worked. When it worked, it would show "Generating secret key" then start the server. Then when my CREATE_ADMIN variable was set in docker-compose.yml it would show in parallel "Creating admin user".

However, now I see only "Generating secret key" then your /usr/bin/entrypoint serves. It appears like it ignores every environment variable, and my admin generation code never runs.

I do not have any idea about where it comes from 😟
Thank you by advance.

Originally created by @w2ak on GitHub (Jun 12, 2018). - Gitea version (or commit ref): docker hub's gitea:latest - Operating system: docker in Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description So I've been using ansible to automatically install *and* configure Gitea. I build my own docker image from gitea and have an entrypoint that creates the admin if necessary. As you can see in my [docker-compose](https://paste.neze.fr/iruxopemam.j2) file, the `INSTALL_LOCK` variable is always set to true. **However, I end up on the Gitea install web page.** As you can see in my [Dockerfile](https://paste.neze.fr/jidofekibe), I only append [app_custom.ini](https://paste.neze.fr/ukifutohuz.j2) to the original default template. This was working before (around may 30 according to my git log). **However, after starting the container, the configuration file only contains the INTERNAL_KEY.** Finally, here is my [docker-entrypoint.sh](https://paste.neze.fr/bepuyivewo.bash). I haven't changed it since the time it worked. When it worked, it would show "Generating secret key" then start the server. Then when my `CREATE_ADMIN` variable was set in `docker-compose.yml` it would show in parallel "Creating admin user". **However, now I see only "Generating secret key" then your `/usr/bin/entrypoint` serves.** It appears like it ignores every environment variable, and my admin generation code never runs. I do not have any idea about where it comes from :worried: Thank you by advance.

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:17:59 -06:00

GiteaMirror closed this issue

2025-11-02 04:17:59 -06:00

GiteaMirror commented

2025-11-02 04:18:00 -06:00

@lunny commented on GitHub (Jun 12, 2018):

What's your latest work instance gitea version?

@lunny commented on GitHub (Jun 12, 2018): What's your latest work instance gitea version?

GiteaMirror commented

2025-11-02 04:18:00 -06:00

@w2ak commented on GitHub (Jun 13, 2018):

If you're asking what is the latest with which it was working, I have been trying to find it but I cannot manage to find it. The problem might come from outside of gitea (docker-compose, the s6 image, etc.), I am just not experienced enough to actually have an idea which is why I am asking the question.

If you're asking what is the latest version I tested, I am testing right now.

WUT! So today's version is 6efdcae, and I don't understand my install worked...

I have another issue but I will file it separately.

Do you have any idea what could be causing this change? I am really surprised...

@w2ak commented on GitHub (Jun 13, 2018): If you're asking what is the latest with which it was working, I have been trying to find it but I cannot manage to find it. The problem might come from outside of gitea (docker-compose, the s6 image, etc.), I am just not experienced enough to actually have an idea which is why I am asking the question. If you're asking what is the latest version I tested, I am testing right now. WUT! So today's version is 6efdcae, and I don't understand my install worked... I have another issue but I will file it separately. Do you have any idea what could be causing this change? I am really surprised...

GiteaMirror commented

2025-11-02 04:18:00 -06:00

@stale[bot] commented on GitHub (Jan 23, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 23, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:18:00 -06:00

@stale[bot] commented on GitHub (Feb 18, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:02:49 -06:00

[PR #1924] [MERGED] Display URLs in integration test logs #16122

Sign in to join this conversation.