3 ms·
what are everyone's thoughts on building containers for running one time binaries? like building a container to run jq or awk or something like that. i've seen
by nunez 9y ago
what are everyone's thoughts on building containers for running one time binaries? like building a container to run jq or awk or something like that.
i've seen this pattern before and it didnt make me feel very good. it reeks of unnecessary complexity.
- majewsky 9y agoDepends on the tool in question. jq or awk are such common-place and light on dependencies that it's indeed unnecessarily complex. The benefit is when a one-time tool is heavy on dependencies. For example, with OpenStack Swift (an S3-like object storage), a common one-time task is swift-ring-builder, which takes an inventory of available storage and creates a shared configuration file which describes how data is shared between storages. That's something you would run on a sysadmin's notebook, but it's included with Swift itself, so you would have to install a bunch of Python modules into a virtualenv. In that case, it's probably easier to just use the Docker image for Swift that you have anyway, and run swift-ring-builder from there.
- nunez 9y agoThanks for the response. I agree that long-running or very heavily-polled services make the most sense for being containerised and that builtins usually don't.