"/usr/bin/entrypoint: exec: line 40: /bin/s6-svscan: not found" on gitea/gitea:1.23.0 docker #13937

New Issue

GiteaMirror · 2025-11-02T10:57:43-06:00

GiteaMirror commented

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

Originally created by @jpraet on GitHub (Jan 9, 2025).

Originally assigned to: @techknowlogick on GitHub.

Description

server_1  | /usr/bin/entrypoint: exec: line 40: /bin/s6-svscan: not found
gitea_server_1 exited with code 127

Gitea Version

1.23.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

gitea/gitea:1.23.0 docker image

Database

None

Originally created by @jpraet on GitHub (Jan 9, 2025). Originally assigned to: @techknowlogick on GitHub. ### Description ``` server_1 | /usr/bin/entrypoint: exec: line 40: /bin/s6-svscan: not found gitea_server_1 exited with code 127 ``` ### Gitea Version 1.23.0 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? gitea/gitea:1.23.0 docker image ### Database None

GiteaMirror added the type/bug label 2025-11-02 10:57:44 -06:00

GiteaMirror closed this issue

2025-11-02 10:57:44 -06:00

GiteaMirror commented

2025-11-02 10:57:45 -06:00

@hemd commented on GitHub (Jan 9, 2025):

+1

@hemd commented on GitHub (Jan 9, 2025): +1

GiteaMirror commented

2025-11-02 10:57:45 -06:00

@joesonshaw commented on GitHub (Jan 9, 2025):

https://github.com/go-gitea/gitea/issues/32954#issuecomment-2558522308

check this, /bin/s6-svscan to /usr/bin/s6-svscan

@joesonshaw commented on GitHub (Jan 9, 2025): https://github.com/go-gitea/gitea/issues/32954#issuecomment-2558522308 check this, `/bin/s6-svscan` to `/usr/bin/s6-svscan`

GiteaMirror commented

2025-11-02 10:57:45 -06:00

@rmi1974 commented on GitHub (Jan 9, 2025):

Just wow. I wonder why this wasn't cherry-picked to 1.23 since it breaks the release for everyone who uses containers (Docker, Podman, lxc). A lot of people use containerized apps because it's the way to go.

EDIT: the fix for "CMD" is there but there is another fix missing for the actual entrypoint script, see my newer comment.

@rmi1974 commented on GitHub (Jan 9, 2025): Just wow. I wonder why this wasn't cherry-picked to 1.23 since it breaks the release for everyone who uses containers (Docker, Podman, lxc). A lot of people use containerized apps because it's the way to go. EDIT: the fix for "CMD" is there but there is another fix missing for the actual entrypoint script, see my newer comment.

GiteaMirror commented

2025-11-02 10:57:45 -06:00

@hemd commented on GitHub (Jan 9, 2025):

service oops, please update docker in dockerhub quickly

@hemd commented on GitHub (Jan 9, 2025): service oops, please update docker in dockerhub quickly

GiteaMirror commented

2025-11-02 10:57:46 -06:00

@wxiaoguang commented on GitHub (Jan 9, 2025):

It seems that the backport is for 1.23 is: Use Alpine 3.21 for the docker images (#32924) #32951

Does 1.23 still lacks the correct patch?

@wxiaoguang commented on GitHub (Jan 9, 2025): It seems that the backport is for 1.23 is: Use Alpine 3.21 for the docker images (#32924) #32951 Does 1.23 still lacks the correct patch?

GiteaMirror commented

2025-11-02 10:57:46 -06:00

@rmi1974 commented on GitHub (Jan 9, 2025):

It seems on that release/v1.23 branch + tag the fix is there:

d670820722 (diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557)

EDIT: But the problem is the actual entrypoint scipt:

68ca73b716/docker/root/usr/bin/entrypoint (L40)

This should have been fixed as well and was entirely missed.

The problem appears for people who customize docker entrypoints, hence "command" is not used but "entrypoint" is overridden to install more dependencies on the base image and/or customize environment.
In my case I inject (env) secrets from a vault secrets container because I don't want to have cleartext passwords passed through environment and/or host bind mounts.

@rmi1974 commented on GitHub (Jan 9, 2025): It seems on that [release/v1.23](https://github.com/go-gitea/gitea/compare/release/v1.23) branch + tag the fix is there: https://github.com/go-gitea/gitea/commit/d670820722bfc475599b847be99ad373dc438a0b#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557 EDIT: But the problem is the actual entrypoint scipt: https://github.com/go-gitea/gitea/blob/68ca73b7169ef4d70ffc9dc6660581da3033e5f7/docker/root/usr/bin/entrypoint#L40 This should have been fixed as well and was entirely missed. The problem appears for people who customize docker entrypoints, hence "command" is not used but "entrypoint" is overridden to install more dependencies on the base image and/or customize environment. In my case I inject (env) secrets from a vault secrets container because I don't want to have cleartext passwords passed through environment and/or host bind mounts.

GiteaMirror commented

2025-11-02 10:57:46 -06:00

@wxiaoguang commented on GitHub (Jan 9, 2025):

@techknowlogick

@wxiaoguang commented on GitHub (Jan 9, 2025): @techknowlogick

GiteaMirror commented

2025-11-02 10:57:47 -06:00

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

Thanks. I've pushed https://github.com/go-gitea/gitea/pull/33185 Additional testing for more use-cases will be included next time. Thanks for reporting the issue :)

@techknowlogick commented on GitHub (Jan 9, 2025): Thanks. I've pushed https://github.com/go-gitea/gitea/pull/33185 Additional testing for more use-cases will be included next time. Thanks for reporting the issue :)

GiteaMirror commented

2025-11-02 10:57:47 -06:00

@diyoyo commented on GitHub (Jan 15, 2025):

Hi, Actually, it was not fixed by 1.23.1.
Yet, I realize there was these lines in my docker-compose.yml, and if I remove the commands, it works properly :

services:
  gitea:
    command:
      - "/bin/s6-svscan"
      - "/etc/s6"

I think they've always been there, but I can't see them in any of the versions available here:
https://docs.gitea.com/1.19/installation/install-with-docker

So : is v1.23.1 really fixed and I had the bug because these lines were overseeding it? Should I just remove these lines or is the documentation out of date?

Thanks.

Cheers

@diyoyo commented on GitHub (Jan 15, 2025): Hi, Actually, it was not fixed by 1.23.1. Yet, I realize there was these lines in my `docker-compose.yml`, and if I remove the commands, it works properly : ``` services: gitea: command: - "/bin/s6-svscan" - "/etc/s6" ``` I think they've always been there, but I can't see them in any of the versions available here: https://docs.gitea.com/1.19/installation/install-with-docker So : is `v1.23.1` really fixed and I had the bug because these lines were overseeding it? Should I just remove these lines or is the documentation out of date? Thanks. Cheers

GiteaMirror commented

2025-11-02 10:57:47 -06:00

@hemd commented on GitHub (Jan 16, 2025):

嗨，实际上，1.23.1 并未修复此问题。不过，我意识到我的中有以下几行docker-compose.yml，如果我删除这些命令，它就可以正常工作：
services:
  gitea:
    command:
      - "/bin/s6-svscan"
      - "/etc/s6"
我认为它们一直都在那里，但我在任何可用版本中都看不到它们：https: //docs.gitea.com/1.19/installation/install-with-docker

那么：是否v1.23.1真的已修复，而我遇到错误是因为这些行过度播种了它？我应该删除这些行吗？还是文档已过时？

谢谢。

干杯

我也是同样的问题，1.23.1并未修复此问题。

@hemd commented on GitHub (Jan 16, 2025): > 嗨，实际上，1.23.1 并未修复此问题。不过，我意识到我的中有以下几行`docker-compose.yml`，如果我删除这些命令，它就可以正常工作： > > ``` > services: > gitea: > command: > - "/bin/s6-svscan" > - "/etc/s6" > ``` > > 我认为它们一直都在那里，但我在任何可用版本中都看不到它们：https: [//docs.gitea.com/1.19/installation/install-with-docker](https://docs.gitea.com/1.19/installation/install-with-docker) > > 那么：是否`v1.23.1`真的已修复，而我遇到错误是因为这些行过度播种了它？我应该删除这些行吗？还是文档已过时？ > > 谢谢。 > > 干杯我也是同样的问题，1.23.1并未修复此问题。

GiteaMirror commented

2025-11-02 10:57:48 -06:00

@wxiaoguang commented on GitHub (Jan 16, 2025):

Why reopen? - "/bin/s6-svscan" shouldn't appear in the docker compose file, or you need to change it to - "/usr/bin/s6-svscan" if you would really like to customize it.

@wxiaoguang commented on GitHub (Jan 16, 2025): Why reopen? `- "/bin/s6-svscan"` shouldn't appear in the docker compose file, or you need to change it to `- "/usr/bin/s6-svscan"` if you would really like to customize it.

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