Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run docker container anymore. #26196

Closed
Unrepentant-Atheist opened this issue Jul 28, 2023 · 1 comment
Closed

Can't run docker container anymore. #26196

Unrepentant-Atheist opened this issue Jul 28, 2023 · 1 comment
Labels

Comments

@Unrepentant-Atheist
Copy link

Unrepentant-Atheist commented 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

@Unrepentant-Atheist
Copy link
Author

Unrepentant-Atheist commented Jul 28, 2023

Solution was here: #25915 (comment)

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant