rewrite docker stuff #42

@xinity commented on GitHub (Nov 7, 2016):

keep s6 as an init replacement.

@xinity commented on GitHub (Nov 7, 2016): keep s6 as an init replacement.

GiteaMirror commented

@xinity commented on GitHub (Nov 7, 2016):

rewrite env variables

@xinity commented on GitHub (Nov 7, 2016): rewrite env variables

GiteaMirror commented

@xinity commented on GitHub (Nov 7, 2016):

dockerfile cleanup

@xinity commented on GitHub (Nov 7, 2016): dockerfile cleanup

GiteaMirror commented

@DblK commented on GitHub (Nov 7, 2016):

I would suggest to have the smaller image as possible and by doing so, the compilation should be done outside and the binary pushed to the docker (maybe from scratch instead alpine).

I could provide later a link to a docker images that can be used to build Go program and make docker images without compiler program.

Edit 11/10/16:
Here is the link to build dockerfile for Go program with image "SCRATCH"

@DblK commented on GitHub (Nov 7, 2016): I would suggest to have the smaller image as possible and by doing so, the compilation should be done outside and the binary pushed to the docker (maybe from scratch instead alpine). I could provide later a link to a docker images that can be used to build Go program and make docker images without compiler program. Edit 11/10/16: Here is the [link](https://github.com/CenturyLinkLabs/golang-builder) to build dockerfile for Go program with image "SCRATCH"

GiteaMirror commented

@xinity commented on GitHub (Nov 7, 2016):

@DblK feel free to update your comment with the appropriate link :)

@xinity commented on GitHub (Nov 7, 2016): @DblK feel free to update your comment with the appropriate link :)

GiteaMirror commented

@tboerger commented on GitHub (Nov 7, 2016):

We will use drone to build the binary outside of the docker image, the drone pipeline is in preparation ;)

@tboerger commented on GitHub (Nov 7, 2016): We will use drone to build the binary outside of the docker image, the drone pipeline is in preparation ;)

GiteaMirror commented

@xinity commented on GitHub (Nov 7, 2016):

@tboerger nice !

then @DblK send the link to me :) i'd be happy to learn moaaarrrr go :)

@xinity commented on GitHub (Nov 7, 2016): @tboerger nice ! then @DblK send the link to me :) i'd be happy to learn moaaarrrr go :)

GiteaMirror commented

@willemvd commented on GitHub (Nov 8, 2016):

why do we need that s6 stuff instead of setting things up in the dockerfile?

@willemvd commented on GitHub (Nov 8, 2016): why do we need that s6 stuff instead of setting things up in the dockerfile?

GiteaMirror commented

@tboerger commented on GitHub (Nov 9, 2016):

@willemvd we need s6 as process manager because we will run more than a single service within the container, at least we need Gitea and openSSH.

@tboerger commented on GitHub (Nov 9, 2016): @willemvd we need s6 as process manager because we will run more than a single service within the container, at least we need Gitea and openSSH.

GiteaMirror commented

@ghost commented on GitHub (Nov 11, 2016):

I would strongly recommend against using scratch as that renders any form of shell scripting invalid.

@ghost commented on GitHub (Nov 11, 2016): I would strongly recommend against using `scratch` as that renders any form of shell scripting invalid.

GiteaMirror commented

@ptman commented on GitHub (Nov 11, 2016):

The way you say it makes it sound like avoiding shell scripts is a bad thing

@ptman commented on GitHub (Nov 11, 2016): The way you say it makes it sound like avoiding shell scripts is a bad thing

GiteaMirror commented

@ghost commented on GitHub (Nov 11, 2016):

Yes, it breaks many things. Including git-hooks and https://github.com/go-gitea/git.

@ghost commented on GitHub (Nov 11, 2016): Yes, it breaks many things. Including git-hooks and https://github.com/go-gitea/git.

GiteaMirror commented