{"id":161,"date":"2019-12-23T09:00:16","date_gmt":"2019-12-23T14:00:16","guid":{"rendered":"http:\/\/blog.voipxswitch.com\/?p=161"},"modified":"2021-01-17T11:25:15","modified_gmt":"2021-01-17T16:25:15","slug":"freeswitch-container-from-scratch-using-dind","status":"publish","type":"post","link":"https:\/\/blog.voipxswitch.com\/?p=161","title":{"rendered":"freeswitch container from scratch using DIND"},"content":{"rendered":"\n

In this post, I’m going to demonstrate how to build a docker container from a scratch<\/a> image that will run FreeSWITCH<\/em>. I’ve always liked scratch because it’s the most minimal docker image available, and in my mind, that really meshes well with the entire concept of docker containers. But I’ll give a bit of my background with scratch and why I’ve used it.<\/p>\n\n\n\n

Scratch is simple with Go<\/em><\/h3>\n\n\n\n

I’ve worked with docker containers as microservices for many years now. And I’ve used go<\/em><\/a> to build 99% of microservices I’ve ever written. Go<\/em> and docker seem to go hand in hand when building microservices. When building microservices written in go<\/em>, the most practical docker image is scratch<\/a>. <\/p>\n\n\n\n

Scratch works great for software written in go<\/em> because go<\/em> doesn’t have any dependencies on external libraries. You can compile your go<\/em> code for the target environment and add the binary to your container based on scratch. Depending on the size of your go<\/em> code, you’ll end up with a container that’s only a few megabytes. <\/p>\n\n\n\n

Example:<\/em><\/p>\n\n\n\n

# compile your go app:\nCGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o myapp<\/pre>\n\n\n\n
Dockerfile<\/em>:<\/p>\n\n\n\n
FROM scratch\nADD myapp \/\nCMD [\"\/myapp\"]<\/pre>\n\n\n\n
Build your container and run it:<\/em><\/p>\n\n\n\n
docker build . -t myapp:latest\ndocker run --rm --name myapp myapp:latest<\/pre>\n\n\n\n
Not so simple with FreeSWITCH<\/em><\/h3>\n\n\n\n
I’ve talked about how easy it is to use scratch with software written in go<\/em>. But when you are dealing with software written in C which require external libraries, like FreeSWITCH<\/em>, it becomes difficult to use the scratch image. The reason for this is, scratch doesn’t come with any<\/strong> libraries at all. This means if you want to use scratch for something like FreeSWITCH<\/em>, you must include those externally linked libraries in your docker container.<\/p>\n\n\n\n
Thankfully, the external libraries FreeSWITCH<\/em> requires are readily available when you install it on Debian. They will automatically be installed when you use the SignalWire apt-get repo. But finding and adding those external libraries into your docker container isn’t so easy.<\/p>\n\n\n\n
I spent a bit of time building FreeSWITCH<\/em> in a container based on a Debian image. Then I stumbled upon the SignalWire<\/a> repo which contained a handy script (make_min_archive.sh<\/a><\/code>) to find all the linked libraries FreeSWITCH<\/em> depends on. I borrowed (and modified) the make_min_archive.sh<\/code> script quite a bit to fit my needs. Once I was able to build FreeSWITCH<\/em> in a Debian based container, I wanted to take it a step further and use scratch. I learned about Docker-In-Docker (DinD) at some point along the way. <\/p>\n\n\n\n
DinD is a method to use a single Dockerfile to run multiple docker images in order to build a single container. With DinD, I used a Debian 10 image to install FreeSWITCH<\/em>, run the make_min_archive.sh<\/code> script to build a binary image which included all linked libraries, then copy the binary over to scratch<\/code> where everything will run. You end up with a 44M image that runs FreeSWITCH<\/em> in docker!<\/p>\n\n\n\n
\"\"
The container listed <none> is the DinD container which uses Debian 10. The size of the FreeSWITCH container is significantly smaller.<\/figcaption><\/figure>\n\n\n\n
\"\"
Dockerfile using DinD<\/figcaption><\/figure>\n\n\n\n
If you’re interested in trying this yourself, I’ve posted my work on github at https:\/\/github.com\/voipxswitch\/freeswitch-docker<\/a>. <\/p>\n","protected":false},"excerpt":{"rendered":"
In this post, I’m going to demonstrate how to build a docker container from a scratch image that will run FreeSWITCH. I’ve always liked scratch because it’s the most minimal docker image available, and in my mind, that really meshes well with the entire concept of docker containers. But I’ll give a bit of my […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,20,25,15],"tags":[],"class_list":["post-161","post","type-post","status-publish","format-standard","hentry","category-docker","category-freeswitch","category-sip","category-voip"],"_links":{"self":[{"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/posts\/161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=161"}],"version-history":[{"count":55,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/posts\/161\/revisions"}],"predecessor-version":[{"id":231,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=\/wp\/v2\/posts\/161\/revisions\/231"}],"wp:attachment":[{"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.voipxswitch.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}