gitea

Dev

Updated yesterday

Gitea Overview

Secure your stack with a hardened Gitea image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Gitea lets teams self-host their own Git repository hosting, code review, and issue tracking instead of relying on GitHub, GitLab, or another third-party service, keeping source code, CI/CD pipelines, and package registries entirely on infrastructure they control. Its low resource footprint means it runs comfortably on hardware too small for heavier alternatives, while still supporting organizations, teams, and fine-grained permissions for larger deployments.

Try It Out

To take the Minimus Gitea image for a test run, we will use Docker Compose to create a self-hosted Gitea instance backed by PostgreSQL.

Step 1 — Configure the Docker Compose file

Save the following code to a new file gitea-compose.yaml in your project directory:

services:
  server:
    image: reg.mini.dev/gitea
    environment:
      - USER_UID=1000
      - USER_GID=1000
      - GITEA__database__DB_TYPE=postgres
      - GITEA__database__HOST=db:5432
      - GITEA__database__NAME=gitea
      - GITEA__database__USER=gitea
      - GITEA__database__PASSWD=Minimus!
    restart: always
    volumes:
      - gitea_data:/data
    ports:
      - "3000:3000"
      - "222:22"
    depends_on:
      - db

  db:
    image: reg.mini.dev/postgres
    restart: always
    environment:
      - POSTGRES_USER=gitea
      - POSTGRES_PASSWORD=Minimus!
      - POSTGRES_DB=gitea
    volumes:
      - gitea_db_data:/var/lib/postgresql/data

volumes:
  gitea_data:
  gitea_db_data:

Step 2 — Start the containers

Run the app:

docker compose -f gitea-compose.yaml up -d

Wait a few seconds for PostgreSQL and Gitea to initialize.

Step 3 — Complete the installation wizard

Visit http://localhost:3000 and follow the installation wizard. The database fields will already be pre-filled from the environment variables set in gitea-compose.yaml.

Clean up

Once ready to clean up, run the following command to remove the containers and their associated volumes:

docker compose -f gitea-compose.yaml down -v

Technical Considerations

The Gitea image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Gitea built by Minimus:

Runs as root to support required functions in alignment with the public image.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.