I had to step away from it because packages are just too old.
They are. You can get .debs through other sources quite often, though.
This is what I specifically hate about building Docker images based on Debian. Half your Dockerfile ends up mucking about with third-party repositories, verifying keys, etc.
Have you considered using testing instead of stable or Siduction?
I should be more clear: specifically I was rebuilding a Docker image based on Debian and needed Node.js for one build step, then Ruby for another as well as the final image.
In the Dockerfile there were a ton of weird commands for simply installing Node.js and Ruby whereas on Alpine Linux I could simply install the needed versions from apk. I understand it’s preferable to build these from scratch but in the case of Node.js I was looking to simply compile a bunch of assets then throw away the layer.
I could’ve spent a bunch of time figuring it out for Debian but I wanted a smaller image in the end anyway too.
I had to step away from it because packages are just too old.
They are. You can get .debs through other sources quite often, though.
This is what I specifically hate about building Docker images based on Debian. Half your
Dockerfileends up mucking about with third-party repositories, verifying keys, etc.Have you considered using
testinginstead ofstableor Siduction?I should be more clear: specifically I was rebuilding a Docker image based on Debian and needed Node.js for one build step, then Ruby for another as well as the final image.
In the
Dockerfilethere were a ton of weird commands for simply installing Node.js and Ruby whereas on Alpine Linux I could simply install the needed versions fromapk. I understand it’s preferable to build these from scratch but in the case of Node.js I was looking to simply compile a bunch of assets then throw away the layer.I could’ve spent a bunch of time figuring it out for Debian but I wanted a smaller image in the end anyway too.