-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Docker image fixes #117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker image fixes #117
Conversation
Current coverage is 3.03% (diff: 100%)@@ master #117 diff @@
========================================
Files 33 33
Lines 8106 8106
Methods 0 0
Messages 0 0
Branches 0 0
========================================
Hits 246 246
Misses 7840 7840
Partials 20 20
|
@@ -21,3 +21,5 @@ ln -sf /data/git /home/git | |||
|
|||
chown -R git:git /data /app/gogs ~git/ | |||
chmod 0755 /data /data/gogs ~git/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't these two lines be changed as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And you'd have to update the Dockerfile as well then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why would this need a change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to be named "gitea" instead of "gogs" ?
make build TAGS="sqlite cert pam" | ||
go install | ||
|
||
# Cleanup GOPATH & vendoring dir | ||
rm -r $GOPATH /app/gogs/vendor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be /app/gitea/vendor ?
i think we should move out of the Dockerfile the build process |
@Xinty Actually, the whole point of a Dockerfile is to allow the user to build the binary him/herself. We should not be putting binaries in there if we can build it ourselves. |
Not sure if I understand @LefsFlarey correctly. But what will happen is that everyone can simply run |
Agree @metalmaze |
Well... I don't know. Building a binary for every OS has to be automated somehow. |
It will be automated, the makefile tasks are already there, just need to add drone as ci |
…rvices syslog-ng, cron and sshd (so it can run on OpenShift v3) * building of gitea is still in the image creation it self, but can be simply be changed when using a pre-build artifact * renamed all folder paths to gitea instead of gogs run with: docker run --rm -p 2222:2222 -p 3000:3000 -v /tmp/docker-ssh-keys:/etc/ssh/keys -v /tmp/docker-data:/data -u $randomHighUserId $buildNumber
# Conflicts: # docker/build.sh
…ocker image build)
…asy to add on runtime)
# Conflicts: # Dockerfile # docker/build.sh # docker/s6/gogs/setup
Changed the whole docker image to be able to run it as unprivileged user (needed for some docker environments like OpenShift v3 which do not allow to run as root) and merged the current master into the pull request |
I'm really not a fan of the current approach. I really dislike the switch away from Alpine. |
@@ -1,22 +1,22 @@ | |||
FROM alpine:3.3 | |||
MAINTAINER [email protected] | |||
FROM willemvd/ubuntu-unprivileged-git-ssh:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This opens up a huge security hole and should not, in any way, be accepted by the maintainers of Gitea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, what's wrong with alpine?
It should definitively be possible to build Gitea on an alpine container without too much hassle. |
So we agree to build only on official images |
Should we take #288 in favor of this? |
Thanks for the work, we have merged #288 now to properly build docker images. |
* use dep instead of govendor * remove example * change dependenci github.com/Unknwon from 1.0 to master
Docker build was broken due to different naming of the artifact from Go, paths changed and glide has been removed.
This should fix these issues (haven't got time to properly test it all)
Signed-off-by: Willem van Dreumel ([email protected])