Rich Freeman on 24 Aug 2016 11:20:53 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Docker Best-practices guide / intro?

On Wed, Aug 24, 2016 at 2:12 PM, Andrew Libby <> wrote:
> On 8/24/16 2:07 PM, Rich Freeman wrote:
> Generally, the image builds are all automated with docker build and
> described in the Dockerfile.

If I wanted to actually do a scripted build I'd probably use Ansible.

>> 2.  Most often my containers will run Gentoo, and building that from
>> scratch every time I want to do updates is going to be time-consuming,
>> and failure-prone.
> Yeah, this is a real head scratcher for me. You could have a gentoo base
> image that you build only once for each update, and then rebuild each
> derived image.  Still the costs are high.  If you're adamant on using s
> source based distro, maybe Docker isn't your best option.

Well, Gentoo already provides a base image (a stage3 tarball).  But,
just adding the application is going to be painful.  And in general I
really don't want to move to Chef/Ansible/etc for what I'm doing.

> Yeah, we've had to adopt the mindset that the only thing holding any
> state exists in a volume mount.  It took a little getting used to
> though, I'll admit.

Yeah, if I had to run 100 Plex servers I'd almost certainly do it this
way.  My problem is that I only want one.  And it is a lot easier to
just manually build a server and deploy incremental updates than to
script the build completely.  My one container runs Arch and getting
that deployed in a container was a pain, since most of the tools for
building Arch containers assume you're running Arch on the host.

I'll probably just stick with privileged nspawn containers for now.
That is until somebody comes up with a nifty tool for creating a uid
map and automatically chowning all the files in the directory tree.

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --