Can't run docker container anymore. #11354

New Issue

GiteaMirror · 2025-11-02T09:35:09-06:00

GiteaMirror commented

2025-11-02 09:35:09 -06:00

Originally created by @Unrepentant-Atheist on GitHub (Jul 28, 2023).

Description

Up until now I had this running flawlessly

---
version: "3"

services:
  server:
    image: gitea/gitea:latest
    container_name: gitea
    restart: always
    ports:
      - 3020:3000
      - 222:22
    environment:
      - USER_UID=1000
      - USER_GID=1000
    labels:
      - deunhealth.restart.on.unhealthy=true
    networks:
      - gitea
    volumes:
      - /home/xxx/docker-data/gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
networks:
  gitea:
    external: false

Now the log in Portainer says:

2023/07/28 08:13:10 ...g/config_provider.go:327:deprecatedSettingFatal() [F] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be/has been removed in v1.19.0. Shutting down

Received signal 15; terminating.

Server listening on :: port 22.

Server listening on 0.0.0.0 port 22

Gitea Version

whatever latest version is pulled from image: gitea/gitea:latest

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

git version 2.34.1 runs on the server / whichever is included in image: gitea/gitea:latest

Operating System

Server runs on Ubuntu 22.04.2 LTS

How are you running Gitea?

Docker container on me server

Database

SQLite

Originally created by @Unrepentant-Atheist on GitHub (Jul 28, 2023). ### Description Up until now I had this running flawlessly ``` --- version: "3" services: server: image: gitea/gitea:latest container_name: gitea restart: always ports: - 3020:3000 - 222:22 environment: - USER_UID=1000 - USER_GID=1000 labels: - deunhealth.restart.on.unhealthy=true networks: - gitea volumes: - /home/xxx/docker-data/gitea:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro networks: gitea: external: false ``` Now the log in Portainer says: ``` 2023/07/28 08:13:10 ...g/config_provider.go:327:deprecatedSettingFatal() [F] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be/has been removed in v1.19.0. Shutting down Received signal 15; terminating. Server listening on :: port 22. Server listening on 0.0.0.0 port 22 ``` ### Gitea Version whatever latest version is pulled from image: gitea/gitea:latest ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version git version 2.34.1 runs on the server / whichever is included in image: gitea/gitea:latest ### Operating System Server runs on Ubuntu 22.04.2 LTS ### How are you running Gitea? Docker container on me server ### Database SQLite

GiteaMirror added the type/bug label 2025-11-02 09:35:09 -06:00

GiteaMirror closed this issue

2025-11-02 09:35:09 -06:00

GiteaMirror commented

2025-11-02 09:35:10 -06:00

@Unrepentant-Atheist commented on GitHub (Jul 28, 2023):

Solution was here: https://github.com/go-gitea/gitea/issues/25915#issuecomment-1640933269

Since I use /home/xxx/docker-data/gitea:/data , I had to go to \home\xxx\docker-data\gitea\gitea\conf\ and make the change in the app.ini

Others will probably have to delve into their docker volumes to change app.ini. I don't use docker volumes in my containers.

@Unrepentant-Atheist commented on GitHub (Jul 28, 2023): Solution was here: https://github.com/go-gitea/gitea/issues/25915#issuecomment-1640933269 Since I use `/home/xxx/docker-data/gitea:/data` , I had to go to `\home\xxx\docker-data\gitea\gitea\conf\` and make the change in the `app.ini` Others will probably have to delve into their docker volumes to change `app.ini`. I don't use docker volumes in my containers.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11354