Different use case. Syncthing just keeps folders "in sync" between two machines even if they are not on the same network. Great tool to always have a backup of pictures taken from your phone to a small raspberry pi running at home for instance.
There is no silver bullet for growth. Some people need to actively seek to be more critical, others need to make that criticism more constructive, or be less harsh on themselves.
Have you considered seeing those lines less as the desirable inner monologue of the person, but rather as an exercise to shift that inner monologue to a more positive mindset ?
I was looking for this exact setup a couple months back. I found a system that works for me, though not exactly perfect.
You can use the extension "Simple Tab Groups"[1] to automatically open some domains in specific Firefox containers like you described, by assigning a container to a group, and then configuring a domain to always open in that group.
The downside is that not all groups will be visible at a time, and you'll need to first select your previous group before finding the tab you came from. For me, that's an acceptable downside given the advantages it brings.
With podman there is no daemon, everything is running as you. The standard setup for docker has a daemon running as root, which means when you start a container it has root privileges.
Not an expert at all, but here's how I would simplify it. All corrections are welcome!
Docker has two main components. The daemon (you can think of it somewhat like a server) and the client (application you use to run commands).
When you install docker on your machine, it generally installs both. The daemon is a process that runs on your local machine and runs as root.
Rootless refers to the alternative method (used by podman for instance) to run the daemon as a standard user, and delegate root-level tasks to something else, like systemd for instance.
> Docker has two main components. The daemon (you can think of it somewhat like a server) and the client (application you use to run commands).
Is the daemon what they call the docker-engine? Is this what's available on Linux natively? Rootless makes sense here bc you wouldn't want one docker image able to interfere with another, or even the Linux system that is running the docker runtime/engine.
For Windows/Mac docker solutions, where does the daemon live/exist/run? Inside a virtualized Linux instance?
As I understand it, most of these alternatives to docker-desktop are all just wrappers around a virtualized Linux image running the docker engine/runtime. That's why many of them require a virtualization engine like Virtual Box. So are these no-commercial solutions just wrappers around one or more virtualized Linux runtimes where the docker engine/runtime is running natively?
If all the above is (approx) correct, then "what" is rootless with this announcement? The docker runtime/engine in the virtualized Linux instance?
I thought the docker engine/runtime on Linux was always able to run rootless docker images. So what is the news here if all these non-commercial solutions are just wrappers around the docker engine/runtime running in a virtualized Linux?
Yes for windows and Mac it runs a Linux VM. On windows it can also use WSL2 as the linux vm.
Docker-engine is the daemon built by docker. Podman is an opensource work a like. Docker-engine doesn't support running as a user other than root. Podman does. This announcement says minikube will work with Podman running as not root.
I remember hearing that development of docker-engine was ceasing, but could obviously live on as it was forked. I guess rootless is some of the work that Docker (company) wanted to keep proprietary and out of this open-source project.
Really quite a shame, although understandable from a commercial perspective.
Assuming that these improvements are finding their way back into an open-source project, I'm glad to hear about this work from minikube and Podman.
