On Thu, Oct 22, 2015 at 10:46:18AM +0200, Magnus Therning wrote: > I've been running GitlabCE in docker for a while now. Using the > instructions at [1] made it amazingly simple and quick to get everything > set up. The only slight irritation is that nothing's on the standard > ports, but I can live with that. > > However, now I started looking into GitlabCI and read that it expects to > run on its own virtual host[2]. Which means I can't really continue with > just passing through a few ports from the host to the container; AFAIU I > need to put the container on an externally visible IP (which I then can > give two names in DNS). > > So then the issue is, how do I tie an IP to a container? > > AFAIU, there is no easy way to accomplish it (i.e. `docker run` doesn't > offer any command line options that will trigger it all to just happen). > But surely there must be some way to achieve it, right?
The method described at [1] seems to work fine :) /M [1]: http://therning.org/magnus/posts/2015-10-22-000-docker-container-with-ip-address-on-local-network.html -- Magnus Therning, magnus.thern...@cipherstone.com Cipherstone Technologies AB Theres Svenssons gata 10, 417 55 Gothenburg, Sweden Beauty is more important in computing than anywhere else in technology because software is so complicated. Beauty is the ultimate defence against complexity. -- David Gelernter -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/20151027122653.GA19494%40sobel.cipherstone.com. For more options, visit https://groups.google.com/d/optout.
