4 ms·

If you have a docker file that can reproduce the VM from scratch then that tends to be pretty decent documentation on the requirements. It might still not work

If you have a docker file that can reproduce the VM from scratch then that tends to be pretty decent documentation on the requirements. It might still not work on your machine, but at least you have a pretty good idea of where to start to get it to.

stavros 3y ago
Just remember to pin absolutely everything. The amount of times stuff broke or was inconsistent because one machine had a different version of the base image than the other...
- ForkMeOnTinder 3y ago
  I fully agree with you. That said, one thing I've come to hate is the proliferation of version numbers in random dockerfiles and random config files all over the place. It's a pain to know what's out of date and a pain to upgrade it all. I wish there was a single tool to manage it all more simply, something like pnpm for containers plus everything you install inside them.
  - earthling8118 3y ago
    Nix. It's the best I've seen for this use case so far. I pin the dependencies using flakes and make container images with specific packages I need It's not 100% perfect for managing exact versions because you update nixpkgs and many packages update as a result, but you can pretty easily pin multiple versions of it or override the version for a specific package
    - stavros 3y ago
      Nix sounds great, unfortunately I never managed to install it reliably.