Feature/docker sock path

[ryck]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Very small PR to change the docker.sock default, as it confuse me today when I try to setup docker notifications

Another way to fix it (and maybe a better one) would be to find out why /var/run/docker.sock is not valid (probably a permissions issue) so feel free to decline this PR

This also needs an small change in the wiki (I did another tiny PR for that too)

Fixes #(issue)
#2061

Type of change

• User interface (UI)
• This change requires a documentation update

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• My changes generate no new warnings

Screenshots (if any)

[louislam]

Uptime Kuma is not a Docker only application. In non-Docker context, it is not a correct path to the docker.sock.

Also, applications such as Portainer and Swarmpit are also using /var/run/docker.sock by default.

docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

docker run -it --rm \
  --name swarmpit-installer \
  --volume /var/run/docker.sock:/var/run/docker.sock \
swarmpit/install:1.9

[ryck]

Fair enough! As I said, probably looking into why the standard path doesn't work is a better option.

Thanks for all your hard work!

[louislam]

Fair enough! As I said, probably looking into why the standard path doesn't work is a better option.

Thanks for all your hard work!

Yes, the hardest part of such issues is that it is not always reproducible.