# Report on using discourse\_docker on a CoreOS image

**URL:** <https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [Setembro 7, 2014, 7:59am UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745 "2014-09-07T07:59:26Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![julsevern](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/julsevern/32/103319_2.png) [@julsevern](https://meta.discourse.org/u/julsevern)\
**Post date:** [Setembro 7, 2014, 7:59am UTC](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745/1 "2014-09-07T07:59:27Z")

</div>

I can happily report that `discourse_docker` works just fine on a CoreOS image. There was exactly one thing I had to modify:

```diff
localhost discourse # git --no-pager diff
diff --git a/launcher b/launcher
index bc7f204..07dca0d 100755
--- a/launcher
+++ b/launcher
@@ -16,7 +16,7 @@ local_discourse=local_discourse
 image=samsaffron/discourse:1.0.3
 docker_path=`which docker.io || which docker`

-docker_ip=`/sbin/ifconfig | \
+docker_ip=`ifconfig | \
                 grep -B1 "inet addr" | \
                 awk '{ if ( $1 == "inet" ) { print $2 } else if ( $2 == "Link" ) { printf "%s:" ,$1 } }' | \
                 grep docker0 | \

```

I had to use current CoreOS alpha release (431.0.0), because this is the first one with Docker 1.2.0. This release uses `btrfs` instead of `aufs`, but it doesn’t cause any kind of issues.

I’d like to follow CoreOS’ way of managing containers, maybe the correct way should be to maintain a private docker registry, and to pull it from there instead.

Thoughts?

---

_[View the full topic](https://meta.discourse.org/t/report-on-using-discourse-docker-on-a-coreos-image/19745)._