Gitea docker container nightly cannot start

[stuzer05]

Description

Possible because of this #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

[stuzer05]

apk add --no-cache s6

fixed the problem

[stuzer05]

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

Created a PR #32955

[pmainvil]

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

[techknowlogick]

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

[pmainvil]

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.

[dgarrison63]

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.

[titleistfour]

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]

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

[pmainvil]

Reverted to 1.23.0 and got it working.

[le-rou]

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

[Tykin]

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

[pmainvil]

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.