# Docker Kibana 5 lacks x-pack? **URL:** \ **Category:** Kibana\ **Created:** [November 15, 2016, 12:24pm UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110 "2016-11-15T12:24:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jmkgreen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmkgreen/32/471_2.png) [@jmkgreen](https://discuss.elastic.co/u/jmkgreen)\ **Post date:** [November 15, 2016, 12:24pm UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/1 "2016-11-15T12:24:03Z")
According to [https://www.elastic.co/guide/en/kibana/current/docker.html](https://www.elastic.co/guide/en/kibana/current/docker.html) the Docker image of Kibana:5 includes x-pack. I accidentally built a container based on kibana:5 and installed x-pack manually. Comparing this with the stock kibana:5 shows x-pack in my image, and missing in the official image. Is this a known bug? I cannot even see within the official Dockerfile where x-pack might be installed... P.S. if I use my own image with x-pack, I cannot launch due to file permission problems. ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [November 15, 2016, 10:10pm UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/2 "2016-11-15T22:10:48Z")
Hi James, Are you getting `docker.elastic.co:kibana/kibana/5.0.1`. see [https://www.elastic.co/guide/en/kibana/current/\_pulling\_the\_image.html](https://www.elastic.co/guide/en/kibana/current/_pulling_the_image.html) regards, Lee ---
**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\ **Post date:** [November 15, 2016, 10:48pm UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/3 "2016-11-15T22:48:09Z")
Yes. It gets a little odd because if you pull `kibana:5` you get the "official" image from Docker Inc. If you pull `docker.elastic.co:kibana/kibana:5.0.1`, you get the "official" image from Elastic, hosted on our dedicated registry. Elastic's image comes with X-Pack, and is built with [this Dockerfile](https://github.com/elastic/kibana-docker/blob/5.x/build/kibana/Dockerfile). ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [November 15, 2016, 11:21pm UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/4 "2016-11-15T23:21:02Z")
I just verified OUR "super-extra-real-deal-official" 5.0.1 Kibana docker image DOES have x-pack installed. 😉 ---
**Author:** ![jmkgreen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmkgreen/32/471_2.png) [@jmkgreen](https://discuss.elastic.co/u/jmkgreen)\ **Post date:** [November 16, 2016, 9:35am UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/5 "2016-11-16T09:35:41Z")
I foresee a world of pain if you expect people to pull from your own repository. I saw the "Pulling the image" page and did not click it as I naturally already knew how to pull the image just as I have always done so - by `kibana:5`. It did not cross my mind that it would instruct me to do anything differently! The very best you can hope for is to patch _their_ README with bold warnings that _this repository_ is not the same as your own one. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 14, 2016, 9:36am UTC](https://discuss.elastic.co/t/docker-kibana-5-lacks-x-pack/66110/6 "2016-12-14T09:36:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.