3 ms·

> Another one is also that Docker is really not pleasant to install on Linux. I'm curious on which Linux did you encounter issues while installing Docker? I ca

> Another one is also that Docker is really not pleasant to install on Linux. I'm curious on which Linux did you encounter issues while installing Docker? I cannot comment on the (to me somewhat pointless) Docker Desktop GUI installation on Linux, but I can confidently report that installing and using docker engine on Ubuntu, at least, is quite trivial and clearly documented[0] on the website. [0] https://docs.docker.com/engine/install/debian/ https://docs.docker.com/engine/install/debian/

AnonCoward42 4y ago
First of: It has been some time since I last installed Docker. It actually was on Ubuntu and a properly current version was not in the distro repositories, so I had to add a new repository and it installed plenty of extra dependencies. It's not hard, but also not really pleasant. It also seems like Docker is now able to run rootless as well, so my nitpicks are actually more minor than I originally thought. It's still not daemonless, but it would work for my use case still I think.
cmeacham98 4y ago
Not them, but my employer makes it a major PITA to add non-standard repositories on the corporate Ubuntu image because of the weird and non-standard way Apt is configured. The "docker.io" package available in the official Ubuntu repository is typically horribly out of date. Additionally, (and admittedly this isn't really Docker's fault), the default IP range for Docker's network happens to conflict with my employer's internal network, which is great fun to debug if you forget to change it.
- vbernat 4y ago
  All LTS versions are using 20.10.12. That's less than one year old. I don't see how horribly out of date this is.
  - cmeacham98 4y ago
    I should have been more specific: It's been a few months (maybe even a year?) since I last checked, but that package used to not include buildx which I need, that's what I meant by out of date.
2OEH8eoCRo0 4y ago
I experienced issues on Fedora because back then Docker did not support cgroups v2.

AnonCoward42 4y ago

First of: It has been some time since I last installed Docker. It actually was on Ubuntu and a properly current version was not in the distro repositories, so I had to add a new repository and it installed plenty of extra dependencies. It's not hard, but also not really pleasant. It also seems like Docker is now able to run rootless as well, so my nitpicks are actually more minor than I originally thought. It's still not daemonless, but it would work for my use case still I think.

cmeacham98 4y ago

Not them, but my employer makes it a major PITA to add non-standard repositories on the corporate Ubuntu image because of the weird and non-standard way Apt is configured. The "docker.io" package available in the official Ubuntu repository is typically horribly out of date. Additionally, (and admittedly this isn't really Docker's fault), the default IP range for Docker's network happens to conflict with my employer's internal network, which is great fun to debug if you forget to change it.

vbernat 4y ago
All LTS versions are using 20.10.12. That's less than one year old. I don't see how horribly out of date this is.
- cmeacham98 4y ago
  I should have been more specific: It's been a few months (maybe even a year?) since I last checked, but that package used to not include buildx which I need, that's what I meant by out of date.

2OEH8eoCRo0 4y ago

I experienced issues on Fedora because back then Docker did not support cgroups v2.