Some file perms are incorrect in the docker image built from Windows

[FlyingOnion]

Gitea Version

1.15.3

Git Version

No response

Operating System

Windows 10 64bit

How are you running Gitea?

Run

git clone --depth 1 --branch v1.15.3 https://github.com/go-gitea/gitea.git
cd gitea
docker build -t mygitea:1.15.3 .

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

Run

docker run --rm --entrypoint ls mygitea:1.15.3 /usr/bin/entrypoint -al
-rw-r--r--    1 root     root           883 Oct 22 14:42 /usr/bin/entrypoint

Screenshots

No response

[FlyingOnion]

If I run it directly it will report an error

docker run -d --rm mygitea:1.15.3
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/usr/bin/entrypoint": permission denied: unknown.

Consider adding RUN chmod 755 /usr/bin/entrypoint after

gitea/Dockerfile

Line 66 in af96286

COPY docker/root /

or use ENTRYPOINT ["sh", "/usr/bin/entrypoint"]

gitea/Dockerfile

Line 63 in af96286

ENTRYPOINT ["/usr/bin/entrypoint"]

[wxiaoguang]

You can not build it from Windows now, otherwise all files under docker/root lose their +x attribute, not only entrypoint. You still meet problems if you only patch the entrypoint.

The question is: should Gitea support to be built from Windows? Need advice from maintainers.

[zeripath]

This particular thing seems like a simple fix without any bad side-effects therefore I think we should do it - however, I think to some extent this building will have to be self-supported.