

I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.
I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.
You’re going to want to look up things like symlinks, hard links, fuse filesystems, and bind mounts among other concepts. Your “whole directory” and other duplicates are artifacts of how the filesystem and process management works, and simply running fsearch or find over them is going to be confusing if you don’t know what you’re looking at.
One Unix concept that carries over to Linux is that everything is a file. Your shared memory space, process data, device driver interfaces, etc, all of it is accessible somewhere in the same virtual filesystem tree as the actual files.
Because of this, there’s very little reason to have the whole filesystem indexed from root. If you’re worried about space usage, you want to work with packages through the package manager. If you’re worried about system integrity, you’ll want package validators.
Because that file is created by the docker.socket service when the service starts and removed when it stops or reboots.
Changing the acl on system files is the wrong way.
Either put your user in the correct group or run docker in rootless mode.
Edit: docker should be the correct group.
https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user
Here you go. Will do specifically what you want, including Web hooks and MQTT out of the box. The Shelly cloud is fine, but these are flashable with tasmota or esphome or roll your own firmware.
I’d imagine tar is included with the install media.
So… you’re afraid of the command that does the thing you’re trying to do?