github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

ssh chroot error when deployed in a podman pod #10815

New Issue
Closed
opened 2025-11-02 09:18:54 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 09:18:54 -06:00
Owner
Copy Link

Originally created by @dchats1 on GitHub (May 9, 2023).

Description

I recently tried setting up Gitea using Podman (v4.4.2) on Fedora Server 37. When I try to clone a repo I get the following error:

$ git clone git@gitea.lab.davidchatterton.com:dchatterton/test.git
Cloning into 'test'...
Connection closed by 172.16.20.70 port 22
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

And in the container logs I see the follow error every time I try to clone a repo:

chroot("/var/empty"): Operation not permitted [preauth]

I've tried with and without selinux enabled. I've also come across a couple related issues, but I haven't been able to come up with a fix for podman:
https://github.com/go-gitea/gitea/issues/15907
https://gitea.com/gitea/helm-chart/issues/8

Gitea Version

1.19

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Fedora Server 37, Podman 4.4.2

How are you running Gitea?

The current deployment is as follows:
Podman Pod:

     "CreateCommand": [
          "podman",
          "pod",
          "create",
          "--name",
          "gitea-pod",
          "--network",
          "prod",
          "--ip",
          "172.16.20.70",
          "--hostname",
          "gitea.lab.davidchatterton.com"
     ],

and the container:

     "CreateCommand": [
          "/usr/bin/podman",
          "run",
          "--cidfile=/run/container-gitea.service.ctr-id",
          "--cgroups=no-conmon",
          "--rm",
          "--sdnotify=conmon",
          "--replace",
          "--detach",
          "--name",
          "gitea-test",
          "--pod",
          "gitea-pod",
          "-v",
          "gitea:/data:z",
           "docker.io/gitea/gitea:latest"
      ],

Database

SQLite

Originally created by @dchats1 on GitHub (May 9, 2023). ### Description I recently tried setting up Gitea using Podman (v4.4.2) on Fedora Server 37. When I try to clone a repo I get the following error: ``` $ git clone git@gitea.lab.davidchatterton.com:dchatterton/test.git Cloning into 'test'... Connection closed by 172.16.20.70 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` And in the container logs I see the follow error every time I try to clone a repo: ``` chroot("/var/empty"): Operation not permitted [preauth] ``` I've tried with and without selinux enabled. I've also come across a couple related issues, but I haven't been able to come up with a fix for podman: https://github.com/go-gitea/gitea/issues/15907 https://gitea.com/gitea/helm-chart/issues/8 ### Gitea Version 1.19 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Fedora Server 37, Podman 4.4.2 ### How are you running Gitea? The current deployment is as follows: Podman Pod: ``` "CreateCommand": [ "podman", "pod", "create", "--name", "gitea-pod", "--network", "prod", "--ip", "172.16.20.70", "--hostname", "gitea.lab.davidchatterton.com" ], ``` and the container: ``` "CreateCommand": [ "/usr/bin/podman", "run", "--cidfile=/run/container-gitea.service.ctr-id", "--cgroups=no-conmon", "--rm", "--sdnotify=conmon", "--replace", "--detach", "--name", "gitea-test", "--pod", "gitea-pod", "-v", "gitea:/data:z", "docker.io/gitea/gitea:latest" ], ``` ### Database SQLite
GiteaMirror added the type/docstype/bug labels 2025-11-02 09:18:54 -06:00
GiteaMirror commented 2025-11-02 09:18:55 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 9, 2023):

Two solutions:

  1. use "gitea:rootless" image
  2. (OR) update the podman to latest version and enable SYS_CHROOT capability (--cap-add=SYS_CHROOT)
@wxiaoguang commented on GitHub (May 9, 2023): Two solutions: 1. use "gitea:rootless" image 2. (OR) update the podman to latest version and enable SYS_CHROOT capability (`--cap-add=SYS_CHROOT`)
GiteaMirror commented 2025-11-02 09:18:56 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 9, 2023):

More details:

  1. By default you are using "gitea:root" image, which uses OpenSSH, while OpenSSH needs "chroot"
  2. Some recent podman removes the SYS_CHROOT support, many user complains, and then podman team added it back
  3. Gitea's rootless image "gitea:rootless" ( helm has image.rootless variable ) doesn't use OpenSSH, so no chroot problem.
@wxiaoguang commented on GitHub (May 9, 2023): More details: 1. By default you are using "gitea:root" image, which uses OpenSSH, while OpenSSH needs "chroot" 2. Some recent podman removes the SYS_CHROOT support, many user complains, and then podman team added it back * https://github.com/containers/common/commit/c700408fdb5aeac5ef024aa7a4bc64abae5ddaab * (maybe) containers-common >= 0.52 3. Gitea's rootless image "gitea:rootless" ( [helm has image.rootless variable](https://gitea.com/gitea/helm-chart/issues/432) ) doesn't use OpenSSH, so no chroot problem.
GiteaMirror commented 2025-11-02 09:18:56 -06:00
Author
Owner
Copy Link

@dchats1 commented on GitHub (May 9, 2023):

Thanks for the quick reply @wxiaoguang! The --cap-add=SYS_CHROOT flag fixed the issue!

@dchats1 commented on GitHub (May 9, 2023): Thanks for the quick reply @wxiaoguang! The `--cap-add=SYS_CHROOT` flag fixed the issue!
GiteaMirror commented 2025-11-02 09:18:56 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 9, 2023):

I think we can keep this issue open, to improve documents.

@wxiaoguang commented on GitHub (May 9, 2023): I think we can keep this issue open, to improve documents.
GiteaMirror commented 2025-11-02 09:18:56 -06:00
Author
Owner
Copy Link

@gorsing commented on GitHub (Jul 20, 2023):

Fix in podman 4.5.1

@gorsing commented on GitHub (Jul 20, 2023): Fix in podman 4.5.1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug type/docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10815
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?