Cannot get passed initial configuration

[tamis-laan]

Description

Using docker (compose) to host gitea:

version: '3'

services:
  gitea:
    image: gitea/gitea:1.16.8
    environment:
      - GITEA__server__PROTOCOL=http
      # - GITEA__server__ROOT_URL=https://git.mydomain.com/
      - GITEA__service__DISABLE_REGISTRATION=1
      - GITEA__repository__DEFAULT_PRIVATE=private
      - GITEA__database__DB_TYPE=sqlite3
    volumes:
      - gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - '3002:3000'
    restart: unless-stopped

volumes:
  gitea:
    name: serv-gitea

On http://server:3002 I find the initial configuration screen. There I add the administrator user, password and email. Pressing the Install Gitea button starts the browser loading but nothing happens. A refresh again shows the initial configuration screen.

Gitea Version

1.16.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Docker container

Database

SQLite

[wxiaoguang]

Please provide logs.

I guess your container can not write files to your volume.

[tamis-laan]

I managed to find the problem, apparently GITEA__database__DB_TYPE=sqlite3 is not allowed. Removing this line reverts to the default which is also sqlite3. Kind of strange that this breaks gitea.

[zeripath]

Removing GITEA__database__DB_TYPE=sqlite3 from the configuration is extremely unlikely to be relevant or have solved anything in and of itself.

Logging would have told us what was happening - and without logs we cannot tell you what has happened or provide any advice.

I'm going to close this - please reopen if you can provide logs.

[wxiaoguang]

I think I find the problem now.

You are using '3002:3000', then you visit 127.0.0.1:3002 to install.

However , after installation, Gitea will auto redirect you to localhost:3000 (aka ROOT_URL), then you will see another fresh Gitea instance.

It's a bug of Gitea's ROOT_URL mechanism.

• Multi-domain support, ROOT_URL problem, use relative URLs in templates instead of absolute URLs #19345
• During new instance setup make 'Gitea Base URL' filled from window.location.origin #20089