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

[jpraet]

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

[hemd]

+1

[joesonshaw]

#32954 (comment)

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

[rmi1974]

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.

[hemd]

service oops, please update docker in dockerhub quickly

[wxiaoguang]

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?

[rmi1974]

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

d670820#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557

EDIT: But the problem is the actual entrypoint scipt:

gitea/docker/root/usr/bin/entrypoint

Line 40 in 68ca73b

exec /bin/s6-svscan /etc/s6

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.

[wxiaoguang]

@techknowlogick

[techknowlogick]

Thanks. I've pushed #33185 Additional testing for more use-cases will be included next time. Thanks for reporting the issue :)

[diyoyo]

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

[hemd]

嗨，实际上，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并未修复此问题。

[wxiaoguang]

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.