{"action":"opened","issue":{"url":"https://api.github.com/repos/coala-analyzer/docker-coala-base/issues/9","repository_url":"https://api.github.com/repos/coala-analyzer/docker-coala-base","labels_url":"https://api.github.com/repos/coala-analyzer/docker-coala-base/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/coala-analyzer/docker-coala-base/issues/9/comments","events_url":"https://api.github.com/repos/coala-analyzer/docker-coala-base/issues/9/events","html_url":"https://github.com/coala-analyzer/docker-coala-base/issues/9","id":160482512,"number":9,"title":"DNS settings for Docker","user":{"login":"stefanoco","id":959880,"avatar_url":"https://avatars.githubusercontent.com/u/959880?v=3","gravatar_id":"","url":"https://api.github.com/users/stefanoco","html_url":"https://github.com/stefanoco","followers_url":"https://api.github.com/users/stefanoco/followers","following_url":"https://api.github.com/users/stefanoco/following{/other_user}","gists_url":"https://api.github.com/users/stefanoco/gists{/gist_id}","starred_url":"https://api.github.com/users/stefanoco/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefanoco/subscriptions","organizations_url":"https://api.github.com/users/stefanoco/orgs","repos_url":"https://api.github.com/users/stefanoco/repos","events_url":"https://api.github.com/users/stefanoco/events{/privacy}","received_events_url":"https://api.github.com/users/stefanoco/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-15T17:45:13Z","updated_at":"2016-06-15T17:45:13Z","closed_at":null,"body":"While using this Docker image for GitLab CI integration I realized that a tricky issue can arise in this setup, while using a private GitLab repo, which is fairly common for closed development.\r\n\r\nNot directly related to this image but a short note can save time here: when using a Docker image for GitLab CI build, the runner will start a new container and from inside the container a ```git clone``` command is the first operation. So from inside the container the GitLan server shoudl be reachable by URI, but sometime the container is not accessing the right DNS service (long story here...) so that a suitable configuration should be applied to the runner by modifying its ```config.toml``` file (usually found inside ```/etc/gitlab```)."}}
{"actor":{"display_login":"stefanoco"}}