<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Cidan</author><text>Pardon me here, but I don&amp;#x27;t understand what you mean by &amp;quot;the docker image most people use is unofficial.&amp;quot;&lt;p&gt;I was under the impression that everyone used the fully featured official docker image (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hub.docker.com&amp;#x2F;r&amp;#x2F;gitlab&amp;#x2F;gitlab-ee&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hub.docker.com&amp;#x2F;r&amp;#x2F;gitlab&amp;#x2F;gitlab-ee&amp;#x2F;&lt;/a&gt;). We&amp;#x27;ve been using this for over a year without issues now. Is there a reason you need the unofficial version? Does it do something different?</text><parent_chain><item><author>contingencies</author><text>@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It&amp;#x27;s painful.&lt;p&gt;The &amp;#x27;quick fix&amp;#x27; for setup these days is supposed to be to use a docker image... but the docker image most people use is unofficial, the maintainer is swamped and has a policy of ignoring problems, and although it runs it doesn&amp;#x27;t work well with real IPs&amp;#x2F;DNS&amp;#x2F;SSL&amp;#x2F;etc. for common cases (eg. email setup silently fails for many and has for ages - see &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;596&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;596&lt;/a&gt; and &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;1005&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;1005&lt;/a&gt; which I recently opened) and adds the docker-is-a-moving-target complexity issue to the potential user&amp;#x27;s stack.&lt;p&gt;Normally I am based in China. Given that Github access is not super fast or stable there, you guys have a great opportunity to take that market. I&amp;#x27;d personally love to use Gitlab both for my own business and those I consult for, but I can&amp;#x27;t get past go with mail on real infrastructure, and experiences with upgrades to date have been terrible.&lt;p&gt;Just offering my own recent experiences as a point of reference.</text></item></parent_chain></comment><story><title>GitLab 8.15 Released</title><url>https://about.gitlab.com/2016/12/22/gitlab-8-15-released/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>CSDude</author><text>We have been using the official Docker image without any problems so far.</text><parent_chain><item><author>contingencies</author><text>@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It&amp;#x27;s painful.&lt;p&gt;The &amp;#x27;quick fix&amp;#x27; for setup these days is supposed to be to use a docker image... but the docker image most people use is unofficial, the maintainer is swamped and has a policy of ignoring problems, and although it runs it doesn&amp;#x27;t work well with real IPs&amp;#x2F;DNS&amp;#x2F;SSL&amp;#x2F;etc. for common cases (eg. email setup silently fails for many and has for ages - see &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;596&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;596&lt;/a&gt; and &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;1005&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sameersbn&amp;#x2F;docker-gitlab&amp;#x2F;issues&amp;#x2F;1005&lt;/a&gt; which I recently opened) and adds the docker-is-a-moving-target complexity issue to the potential user&amp;#x27;s stack.&lt;p&gt;Normally I am based in China. Given that Github access is not super fast or stable there, you guys have a great opportunity to take that market. I&amp;#x27;d personally love to use Gitlab both for my own business and those I consult for, but I can&amp;#x27;t get past go with mail on real infrastructure, and experiences with upgrades to date have been terrible.&lt;p&gt;Just offering my own recent experiences as a point of reference.</text></item></parent_chain></comment><story><title>GitLab 8.15 Released</title><url>https://about.gitlab.com/2016/12/22/gitlab-8-15-released/</url></story>