Installation with Docker

Gitea provides automatically updated Docker images within its Docker Hub organization. It is possible to always use the latest stable tag or to use another service that handles updating Docker images.

The rootless image uses Gitea internal SSH to provide Git protocol and doesn’t support OpenSSH.

This reference setup guides users through the setup based on docker-compose, but the installation of docker-compose is out of scope of this documentation. To install docker-compose itself, follow the official install instructions.

Basics

The most simple setup just creates a volume and a network and starts the gitea/gitea:latest-rootless image as a service. Since there is no database available, one can be initialized using SQLite3.

Create a directory for data and config:

  1. mkdir -p gitea/{data,config}
  2. cd gitea
  3. touch docker-compose.yml

Then paste the following content into a file named docker-compose.yml:

  1. version: "2"
  3. services:
  4.   server:
  5.     image: gitea/gitea:1.19.4-rootless
  6.     restart: always
  7.     volumes:
  8.       - ./data:/var/lib/gitea
  9.       - ./config:/etc/gitea
  10.       - /etc/timezone:/etc/timezone:ro
  11.       - /etc/localtime:/etc/localtime:ro
  12.     ports:
  13.       - "3000:3000"
  14.       - "2222:2222"

Note that the volume should be owned by the user/group with the UID/GID specified in the config file. By default Gitea in docker will use uid:1000 gid:1000. If needed you can set ownership on those folders with the command:

  1. sudo chown 1000:1000 config/ data/

If you don’t give the volume correct permissions, the container may not start.

For a stable release you could use :latest-rootless, :1-rootless or specify a certain release like :1.19.4-rootless, but if you’d like to use the latest development version then :nightly-rootless would be an appropriate tag. If you’d like to run the latest commit from a release branch you can use the :1.x-nightly-rootless tag, where x is the minor version of Gitea. (e.g. :1.16-nightly-rootless)

Custom port

To bind the integrated ssh and the webserver on a different port, adjust the port section. It’s common to just change the host port and keep the ports within the container like they are.

  1. version: "2"
  3. services:
  4.   server:
  5.     image: gitea/gitea:1.19.4-rootless
  6.     restart: always
  7.     volumes:
  8.       - ./data:/var/lib/gitea
  9.       - ./config:/etc/gitea
  10.       - /etc/timezone:/etc/timezone:ro
  11.       - /etc/localtime:/etc/localtime:ro
  12.     ports:
  13. -      - "3000:3000"
  14. -      - "2222:2222"
  15. +      - "80:3000"
  16. +      - "22:2222"

MySQL database

To start Gitea in combination with a MySQL database, apply these changes to the docker-compose.yml file created above.

  1. version: "2"
  3. services:
  4.   server:
  5.     image: gitea/gitea:1.19.4-rootless
  6. +    environment:
  7. +      - GITEA__database__DB_TYPE=mysql
  8. +      - GITEA__database__HOST=db:3306
  9. +      - GITEA__database__NAME=gitea
  10. +      - GITEA__database__USER=gitea
  11. +      - GITEA__database__PASSWD=gitea
  12.     restart: always
  13.     volumes:
  14.       - ./data:/var/lib/gitea
  15.       - ./config:/etc/gitea
  16.       - /etc/timezone:/etc/timezone:ro
  17.       - /etc/localtime:/etc/localtime:ro
  18.     ports:
  19.       - "3000:3000"
  20.       - "222:22"
  21. +    depends_on:
  22. +      - db
  23. +
  24. +  db:
  25. +    image: mysql:8
  26. +    restart: always
  27. +    environment:
  28. +      - MYSQL_ROOT_PASSWORD=gitea
  29. +      - MYSQL_USER=gitea
  30. +      - MYSQL_PASSWORD=gitea
  31. +      - MYSQL_DATABASE=gitea
  32. +    volumes:
  33. +      - ./mysql:/var/lib/mysql

PostgreSQL database

To start Gitea in combination with a PostgreSQL database, apply these changes to the docker-compose.yml file created above.

  1. version: "2"
  3. services:
  4.   server:
  5.     image: gitea/gitea:1.19.4-rootless
  6.     environment:
  7. +      - GITEA__database__DB_TYPE=postgres
  8. +      - GITEA__database__HOST=db:5432
  9. +      - GITEA__database__NAME=gitea
  10. +      - GITEA__database__USER=gitea
  11. +      - GITEA__database__PASSWD=gitea
  12.     restart: always
  13.     volumes:
  14.       - ./data:/var/lib/gitea
  15.       - ./config:/etc/gitea
  16.       - /etc/timezone:/etc/timezone:ro
  17.       - /etc/localtime:/etc/localtime:ro
  18.     ports:
  19.       - "3000:3000"
  20.       - "2222:2222"
  21. +    depends_on:
  22. +      - db
  23. +
  24. +  db:
  25. +    image: postgres:14
  26. +    restart: always
  27. +    environment:
  28. +      - POSTGRES_USER=gitea
  29. +      - POSTGRES_PASSWORD=gitea
  30. +      - POSTGRES_DB=gitea
  31. +    volumes:
  32. +      - ./postgres:/var/lib/postgresql/data

Named volumes

To use named volumes instead of host volumes, define and use the named volume within the docker-compose.yml configuration. This change will automatically create the required volume. You don’t need to worry about permissions with named volumes; Docker will deal with that automatically.

  1. version: "2"
  3. +volumes:
  4. +  gitea-data:
  5. +    driver: local
  6. +  gitea-config:
  7. +    driver: local
  8. +
  9. services:
  10.   server:
  11.     image: gitea/gitea:1.19.4-rootless
  12.     restart: always
  13.     volumes:
  14. -      - ./data:/var/lib/gitea
  15. +      - gitea-data:/var/lib/gitea
  16. -      - ./config:/etc/gitea
  17. +      - gitea-config:/etc/gitea
  18.       - /etc/timezone:/etc/timezone:ro
  19.       - /etc/localtime:/etc/localtime:ro
  20.     ports:
  21.       - "3000:3000"
  22.       - "2222:2222"

MySQL or PostgreSQL containers will need to be created separately.

Custom user

You can choose to use a custom user (following —user flag definition https://docs.docker.com/engine/reference/run/#user). As an example to clone the host user git definition use the command id -u git and add it to docker-compose.yml file: Please make sure that the mounted folders are writable by the user.

  1. version: "2"
  3. services:
  4.   server:
  5.     image: gitea/gitea:1.19.4-rootless
  6.     restart: always
  7. +    user: 1001
  8.     volumes:
  9.       - ./data:/var/lib/gitea
  10.       - ./config:/etc/gitea
  11.       - /etc/timezone:/etc/timezone:ro
  12.       - /etc/localtime:/etc/localtime:ro
  13.     ports:
  14.       - "3000:3000"
  15.       - "2222:2222"

Start

To start this setup based on docker-compose, execute docker-compose up -d, to launch Gitea in the background. Using docker-compose ps will show if Gitea started properly. Logs can be viewed with docker-compose logs.

To shut down the setup, execute docker-compose down. This will stop and kill the containers. The volumes will still exist.

Notice: if using a non-3000 port on http, change app.ini to match LOCAL_ROOT_URL = http://localhost:3000/.

Install

After starting the Docker setup via docker-compose, Gitea should be available using a favorite browser to finalize the installation. Visit http://server-ip:3000 and follow the installation wizard. If the database was started with the docker-compose setup as documented above, please note that db must be used as the database hostname.

Customization

Customization files described here should be placed in /var/lib/gitea/custom directory. If using host volumes, it’s quite easy to access these files; for named volumes, this is done through another container or by direct access at /var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea. The configuration file will be saved at /etc/gitea/app.ini after the installation.

Upgrading

❗❗ Make sure you have volumed data to somewhere outside Docker container ❗❗

To upgrade your installation to the latest release:

  1. # Edit `docker-compose.yml` to update the version, if you have one specified
  2. # Pull new images
  3. docker-compose pull
  4. # Start a new container, automatically removes old one
  5. docker-compose up -d

Upgrading from standard image

  • Backup your setup
  • Change volume mountpoint from /data to /var/lib/gitea
  • If you used a custom app.ini move it to a new volume mounted to /etc/gitea
  • Rename folder (inside volume) gitea to custom
  • Edit app.ini if needed
    • Set START_SSH_SERVER = true
  • Use image gitea/gitea:1.19.4-rootless

Managing Deployments With Environment Variables

In addition to the environment variables above, any settings in app.ini can be set or overridden with an environment variable of the form: GITEA__SECTION_NAME__KEY_NAME. These settings are applied each time the docker container starts. Full information here.

These environment variables can be passed to the docker container in docker-compose.yml. The following example will enable an smtp mail server if the required env variables GITEA__mailer__FROM, GITEA__mailer__HOST, GITEA__mailer__PASSWD are set on the host or in a .env file in the same directory as docker-compose.yml:

  1. ...
  2. services:
  3.   server:
  4.     environment:
  5.       - GITEA__mailer__ENABLED=true
  6.       - GITEA__mailer__FROM=${GITEA__mailer__FROM:?GITEA__mailer__FROM not set}
  7.       - GITEA__mailer__MAILER_TYPE=smtp
  8.       - GITEA__mailer__HOST=${GITEA__mailer__HOST:?GITEA__mailer__HOST not set}
  9.       - GITEA__mailer__IS_TLS_ENABLED=true
  10.       - GITEA__mailer__USER=${GITEA__mailer__USER:-apikey}
  11.       - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}"""

To set required TOKEN and SECRET values, consider using Gitea’s built-in generate utility functions.

SSH Container Passthrough

Since SSH is running inside the container, SSH needs to be passed through from the host to the container if SSH support is desired. One option would be to run the container SSH on a non-standard port (or moving the host port to a non-standard port). Another option which might be more straightforward is to forward SSH commands from the host to the container. This setup is explained in the following.

This guide assumes that you have created a user on the host called git with permission to run docker exec, and that the Gitea container is called gitea. You will need to modify that user’s shell to forward the commands to the sh executable inside the container, using docker exec.

First, create the file /usr/local/bin/gitea-shell on the host, with the following contents:

  1. #!/bin/sh
  2. /usr/bin/docker exec -i --env SSH_ORIGINAL_COMMAND="$SSH_ORIGINAL_COMMAND" gitea sh "$@"

Note that gitea in the docker command above is the name of the container. If you named yours differently, don’t forget to change that.

You should also make sure that you’ve set the permissions of the shell wrapper correctly:

  1. sudo chmod +x /usr/local/bin/gitea-shell

Once the wrapper is in place, you can make it the shell for the git user:

  1. sudo usermod -s /usr/local/bin/gitea-shell git

Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the SSH AuthorizedKeysCommand to match the keys against those accepted by Gitea. Add the following block to /etc/ssh/sshd_config, on the host:

  1. Match User git
  2.   AuthorizedKeysCommandUser git
  3.   AuthorizedKeysCommand /usr/bin/docker exec -i gitea /usr/local/bin/gitea keys -c /etc/gitea/app.ini -e git -u %u -t %t -k %k

(From 1.16.0 you will not need to set the -c /etc/gitea/app.ini option.)

All that is left to do is restart the SSH server:

  1. sudo systemctl restart sshd

Notes

This isn’t actually using the docker SSH - it is simply using the commands around it. You could theoretically not run the internal SSH server.