Gitea docker container nightly cannot start #13871

New Issue

GiteaMirror · 2025-11-02T10:55:40-06:00

GiteaMirror commented

2025-11-02 10:55:40 -06:00

Originally created by @stuzer05 on GitHub (Dec 22, 2024).

Description

Possible because of this https://github.com/go-gitea/gitea/pull/32924

/usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

Gitea Version

image id 9981acd570bf

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

None

Originally created by @stuzer05 on GitHub (Dec 22, 2024). ### Description Possible because of this https://github.com/go-gitea/gitea/pull/32924 ``` /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found ``` ### Gitea Version image id 9981acd570bf ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? docker ### Database None

GiteaMirror added the type/bug issue/workaround labels 2025-11-02 10:55:40 -06:00

GiteaMirror closed this issue

2025-11-02 10:55:40 -06:00

GiteaMirror commented

2025-11-02 10:55:41 -06:00

@stuzer05 commented on GitHub (Dec 22, 2024):

apk add --no-cache s6

fixed the problem

@stuzer05 commented on GitHub (Dec 22, 2024): ``` apk add --no-cache s6 ``` fixed the problem

GiteaMirror commented

2025-11-02 10:55:41 -06:00

@stuzer05 commented on GitHub (Dec 22, 2024):

Actually the path was the problem, /bin/s6-svscan -> /usr/bin/s6-svscan

Created a PR https://github.com/go-gitea/gitea/pull/32955

@stuzer05 commented on GitHub (Dec 22, 2024): Actually the path was the problem, `/bin/s6-svscan` -> `/usr/bin/s6-svscan` Created a PR https://github.com/go-gitea/gitea/pull/32955

GiteaMirror commented

2025-11-02 10:55:41 -06:00

@pmainvil commented on GitHub (Jan 31, 2025):

After updating image to gitea-latest, I get the following error on a Synology DSM 7.2.1 and the container stops.

/usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

@pmainvil commented on GitHub (Jan 31, 2025): After updating image to gitea-latest, I get the following error on a Synology DSM 7.2.1 and the container stops. /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

GiteaMirror commented

2025-11-02 10:55:41 -06:00

@techknowlogick commented on GitHub (Jan 31, 2025):

@pmainvil Your configuration has a hardcoded endpoint, please either let the image use the default, or update it to the new location.

@techknowlogick commented on GitHub (Jan 31, 2025): @pmainvil Your configuration has a hardcoded endpoint, please either let the image use the default, or update it to the new location.

GiteaMirror commented

2025-11-02 10:55:41 -06:00

@pmainvil commented on GitHub (Jan 31, 2025):

No change to the "gitea/gitea latest" image settings loaded many months ago. I simply upgraded the image to the latest version and it stopped working. I had done multiple updates without over time without any problems.

@pmainvil commented on GitHub (Jan 31, 2025): No change to the "gitea/gitea latest" image settings loaded many months ago. I simply upgraded the image to the latest version and it stopped working. I had done multiple updates without over time without any problems. ![Image](https://github.com/user-attachments/assets/50d51b04-bded-41b9-bb0a-1ed5e3e78efc)

GiteaMirror commented

2025-11-02 10:55:42 -06:00

@dgarrison63 commented on GitHub (Jan 31, 2025):

I'm having the exact same issue as @pmainvil in that I upgraded gitea which is running on my Synology NAS. Prior to the upgrade of the image, no issues at all.

The error messages i'm getting are this: /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

I have not hardcoded anything and just left everything at the defaults in terms of entrypoint.

@dgarrison63 commented on GitHub (Jan 31, 2025): I'm having the exact same issue as @pmainvil in that I upgraded gitea which is running on my Synology NAS. Prior to the upgrade of the image, no issues at all. The error messages i'm getting are this: /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found I have not hardcoded anything and just left everything at the defaults in terms of entrypoint.

GiteaMirror commented

2025-11-02 10:55:42 -06:00

@titleistfour commented on GitHub (Feb 1, 2025):

Exactly the same issue for me. No changes from the default. An update on Synology DSM 7.2.1 just broke my gitea container with the same error message: /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

@titleistfour commented on GitHub (Feb 1, 2025): Exactly the same issue for me. No changes from the default. An update on Synology DSM 7.2.1 just broke my gitea container with the same error message: /usr/bin/entrypoint: exec: line 38: /bin/s6-svscan: not found

GiteaMirror commented

2025-11-02 10:55:42 -06:00

@titleistfour commented on GitHub (Feb 1, 2025):

I ended up reverting to a previous specific tag version and that got my container back online.

@titleistfour commented on GitHub (Feb 1, 2025): I ended up reverting to a previous specific tag version and that got my container back online.

GiteaMirror commented

2025-11-02 10:55:42 -06:00

@pmainvil commented on GitHub (Feb 1, 2025):

Reverted to 1.23.0 and got it working.

@pmainvil commented on GitHub (Feb 1, 2025): Reverted to 1.23.0 and got it working.

GiteaMirror commented

2025-11-02 10:55:43 -06:00

@le-rou commented on GitHub (Feb 3, 2025):

Same for me: Synology NAS, Portainer, same error message. I didn't set up anything custom. However, I noticed that the CMD was correct in the image, but not in the container - turned out, there was an override after all.
Fixed it like this:

open gitea container
click duplicate/edit
under advanced: set Command and Entrypoint to default instead of override
deployed under new name for safety

@le-rou commented on GitHub (Feb 3, 2025): Same for me: Synology NAS, Portainer, same error message. I didn't set up anything custom. However, I noticed that the CMD was correct in the image, but not in the container - turned out, there was an override after all. Fixed it like this: - open gitea container - click duplicate/edit - under advanced: set Command and Entrypoint to default instead of override - deployed under new name for safety

GiteaMirror commented

2025-11-02 10:55:43 -06:00

@Tykin commented on GitHub (Feb 6, 2025):

Same for me: Synology NAS, Portainer, same error message. I didn't set up anything custom. However, I noticed that the CMD was correct in the image, but not in the container - turned out, there was an override after all. Fixed it like this:

open gitea container

click duplicate/edit

under advanced: set Command and Entrypoint to default instead of override

deployed under new name for safety

If you are using Container Manager, I took the following steps:

Export your gitea container settings to json
Open the json and remove line
"cmd" : "/bin/s6-svscan /etc/s6",
Import the json as a new container
You may need to change your ports in the old container to free them up for the new container

@Tykin commented on GitHub (Feb 6, 2025): > Same for me: Synology NAS, Portainer, same error message. I didn't set up anything custom. However, I noticed that the CMD was correct in the image, but not in the container - turned out, there was an override after all. Fixed it like this: > > * open gitea container > * click duplicate/edit > * under advanced: set Command and Entrypoint to default instead of override > * deployed under new name for safety If you are using Container Manager, I took the following steps: * Export your gitea container settings to json * Open the json and remove line "cmd" : "/bin/s6-svscan /etc/s6", * Import the json as a new container * You may need to change your ports in the old container to free them up for the new container

GiteaMirror commented

2025-11-02 10:55:43 -06:00

@pmainvil commented on GitHub (Feb 6, 2025):

Was about to try your workaround, but updated/tested latest (1.23.3) and it worked OK. All from container creation using the Container Manager.

@pmainvil commented on GitHub (Feb 6, 2025): Was about to try your workaround, but updated/tested latest (1.23.3) and it worked OK. All from container creation using the Container Manager.

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#13871