Re:Aptly: Owning Your Debian Distribution
by qwerta on Saturday October 11, 2014 @08:37AM
(#8441982)
I think I will stick with a Docker. DEB packages are very complicated and this tool does not really handle dependency conflits and so on that well. Plus it does not work with RPM and other packages systems.
Re:Aptly: Owning Your Debian Distribution
by icebraining on Saturday October 11, 2014 @09:38AM
(#8442092)
DEB packages are very complicated
Not really, it's just a tar file with some metadata. Using fpm¹, making packages from a directory is extremely simple. I've been building internal packages from our different components, and the build script only has three or four lines. And besides, even Dockerfiles often use apt/yum.
I use fpm to build aptly .deb packages, it is extremely simple to use compared to usual source package + build path.
This is a problem for Go programs, due to multiple unversioned (usually) dependencies on other Go libraries.
Re:Aptly: Owning Your Debian Distribution
by robinson-wall on Saturday October 11, 2014 @09:45AM
(#8442111)
I'm currently working on transitioning to a Docker-based infrastructure. My existing system builds .debs and pushes them to an internal repository (reprepro rather than aptly because aptly was in its infancy when I built it).
I'm not going to be building .debs for installation inside Docker containers (turtles all the way down) but I would still consider something like aptly for storing and managing any obscure dependencies that my applications might require, and for maintaining a mirror on the local network to speed up image builds.
Docker is for deployment, it works in terms of graphs of filesystem images. The tools do slightly overlap in use case, but they operate in entirely different domains.
It wouldn't be unreasonable to mix both in the same project, but there is no hard rule for when this would be appropriate.