Docker\u00a0is seeing rapid adoption among the software development world. So far it seems to me a very nice way to make software installation much less painful, but there\u00a0is still plenty of room for improvement.<\/p>\n
If you’re running Linux then you can stop reading now.\u00a0Docker<\/a>\u00a0is an abstraction layer over Linux Containers<\/a> (LXC), they’ve also created a repository <\/a>where pre-defined containers can be found – you can even add your own.\u00a0LXC is cool stuff, but it does mean\u00a0Docker\u00a0runs Linux.<\/p>\n Windows and OSX users need to use boot2docker<\/a>, a\u00a0Tiny Core Linux virtual machine that\u00a0has just enough stuff to run docker.\u00a0This is\u00a0a fine solution but often when people ask about missing tools inside of boot2docker, the answer is to install a container that has the tools you want and run inside of that container. Things quickly start to feel like\u00a0Inception<\/a>.<\/p>\n Boot2docker is based on Tiny Core Linux<\/a>,\u00a0so you can use the tce-load utility to install additional components if needed. So say we wanted to run Perl:<\/p>\n You can sniff around\u00a0the repository<\/a> to figure out what packages are available.<\/p>\n There is documentation on adding a persistent partition<\/a> to your boot2docker setup. This is useful if you want to run the\u00a0tce-load every time you run without having to type it in each time. Getting this setup is a little bit fiddly,\u00a0and if we’re clever we can do something a bit cooler.<\/p>\n Let’s build a custom\u00a0boot2docker.iso file! The build process is nicely documented<\/a>. We can use a Dockerfile <\/a>to create our own iso with the packages we want.<\/p>\n Before we start, you will want to make sure that your boot2docker is running with enough resources. The default should be 2048MB which should\u00a0work, you will also need enough disk space on \/var\/lib\/docker\/aufs inside boot2docker. \u00a0If you have problems consider\u00a0changing your configuration<\/a>.<\/p>\n Create a Dockerfile with the following contents:<\/p>\n Then follow the boot2docker.iso build process<\/a>.<\/p>\n The The The last two steps “build\u00a0the iso” are lifted directly from the same boot2docker Dockerfile, these are the steps required to actually\u00a0create the iso file.<\/p>\n Figuring out how to run the boot2docker.iso I’ll leave as an exercise for the reader.<\/p>\n","protected":false},"excerpt":{"rendered":" Docker\u00a0is seeing rapid adoption among the software development world. So far it seems to me a very nice way to make software installation much less painful, but there\u00a0is still plenty of room for improvement. If you’re running Linux then you can stop reading now.\u00a0Docker\u00a0is an abstraction layer over Linux Containers (LXC), they’ve also created a … Continue reading “Adding a package to boot2docker”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12,14],"tags":[],"class_list":["post-1467","post","type-post","status-publish","format-standard","hentry","category-how-to","category-work"],"_links":{"self":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/comments?post=1467"}],"version-history":[{"count":5,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1467\/revisions"}],"predecessor-version":[{"id":1474,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1467\/revisions\/1474"}],"wp:attachment":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/media?parent=1467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/categories?post=1467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/tags?post=1467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}$ tce-load -wi perl5<\/code><\/p>\nFROM boot2docker\/boot2docker<\/code><\/span><\/p>\n# Append indicator this is modified image
\nRUN echo \"\\nMy modified boot2docker.iso\\n\" >> $ROOTFS\/etc\/motd
\n<\/code><\/span><\/p>\n# Install perl5
\nRUN curl -L -o \/tmp\/perl5.tcz $TCL_REPO_BASE\/tcz\/perl5.tcz && \\
\nunsquashfs -f -d $ROOTFS \/tmp\/perl5.tcz && \\
\nrm -rf \/tmp\/perl5.tcz
\n<\/code><\/span><\/p>\n# build the iso
\nRUN \/make_iso.sh
\nCMD [\"cat\", \"boot2docker.iso\"]<\/code><\/span><\/p>\n$ sudo docker build -t my-boot2docker-img .
\n$ sudo docker run --rm my-boot2docker-img > boot2docker.iso<\/code><\/p>\nFROM<\/code> is used to declare the base image we want to start from. We’re building\u00a0our new container on this base.<\/p>\nRUN<\/code> directive is executed against the current image at build time. In this case we can’t use tce-load<\/code> since we’re not actually running Tiny Core Linux at this point, we’re running against the docker image we are building. This is why we’re doing the installation of perl\u00a0manually. I based the installation from the boot2docker DockerFile<\/a>.<\/p>\n