

I’m almost sure that ./
is the directory of the compose.yaml.
Normally I just run docker compose up -d
in the project directory, but I could run docker compose up -d -f /somewhere/compose.yaml
from another directory, and then the ./
would be /somewhere
, and not the directory where I started the command.
Here it is.
Apparently there are concerns that a site could be compromised, and then it would be able to do bad things to one of your USB devices, after you gave the permission to access that one USB device.
So now the users just download an executable and run it, that’s clearly better. Or they have to use Chrome.