181–190 of 202 posts
Talking about containers: is there an easy way to run “system” containers? This is, containers that run systemd and everything else you would expect to be running on a normal Linux OS. I rely heavily on VMs to simulate cloud environments, but I would love to use lightweight containers instead. Also, these “system” containers should be able to run containers inside them as well (docker in docker?). I saw something on…
Earlier quoted context omitted.
On windows, docker desktop can use Hyper-V, but it also supports WSL2 as a backend.
The DD WSL2 backend is also creating a VM in Hyper-V. Actually, it's creating two VMs (docker-desktop and docker-desktop-data). It's also running a proxy in your WSL2 VM so you can access the docker server. It's all a bit convoluted TBH. I actually decided today to stop using DD on my Windows machine and just run docker native inside the WSL2 VM instance instead. Still not sure what solution I'm going for on my Mac.
Earlier quoted context omitted.
Best part: it's QEMU so you can choose your CPU architecture and run x86_64 containers on ARM Macs
x86_64 containers on ARM mac are extremely slow.
Earlier quoted context omitted.
Best part: it's QEMU so you can choose your CPU architecture and run x86_64 containers on ARM Macs
x86_64 containers on ARM mac are extremely slow.
I also never understood the justification for the added complexity it created, but I also don't have a dedicated ops team at my job to solve my problems.
Earlier quoted context omitted.
> For personal use I found it great and lighter than Docker Desktop. I don't know what Docker Desktop is doing but on a top end i9 with 128gb of ram it still takes 60 seconds to start and the UI takes forever to do anything it makes Teams look responsive
I user Rancher Desktop on an i9 with 32gb of RAM. Starts in less than a minute. I also have Teams and slack. Sometimes I have over 200 browser tabs open (yes, I have a problem). The UI is responsive pretty quickly. A lot of delays has to do with starting VMs. You need this for Linux on Mac/Windows. Disclaimer: I started Rancher Desktop. I might be biased.
This is where those extensions (or native Firefox) is good for auto-sleeping tabs you haven't looked at in the last 10-20min. Saves so much CPU.
My use case is the simplest of them all:
A docker compose file for postgres12 with a folder attached as permanent volume.
- colima couldnt do chmod, and it failed when i tried to restore database to folder. I tracked an issue on github, known stuff, issue is couple of years old.
- podman made it work somehow, data restore was under way - it run out of file descriptors, again - know bug with postgres and other scenarios, tracked on github for few years.
turned off, fired docker again, it works.
meh :(
Earlier quoted context omitted.
If you want something as non-root to bind below 1024, there's a sysctl for it.[1] Docker bypasses this essentially because it uses root privs to set up the port forwarding rules. [1]: https://www.kernel.org/doc/html/latest/networking/ip-sysctl.... -> ip_unprivileged_port_start
It's not enough in some cases, in a multi container pod (with `podman play kube`) I still got permission issues binding to privileged ports (which were permitted by the sysctl). There was some github issue about it. In my experience, if you need to bind to < 1024 ports, just run the container as root. Also if you want finer-grained control of host-side permissions of your mounts (i.e. map host uid 1000 to container u…
I did a quick test and it works ok for me to bind to low numbered ports just passing that param to podman run.
docker is free..?