mirror of
https://github.com/jokob-sk/NetAlertX.git
synced 2026-10-28 20:11:18 -04:00
DOCS: permissions on Synology
This commit is contained in:
1 parent
86ac9c3b2f
commit
7bb7ce9c8d
2 files changed
+14
-7
No files matched your search
@@ -51,6 +51,9 @@ See alternative [docker-compose examples](https://docs.netalertx.com/DOCKER_COMP
|
||||
|
||||
### Docker environment variables
|
||||
|
||||
> [!NOTE]
|
||||
> If you see only 2 devices, you might need to run the container as root by setting a custom `PUID` and `PGID` as some systems don't support `--cap-add` properly, such as some Synology setups. See [running as root](https://docs.netalertx.com/FILE_PERMISSIONS/#running-as-root).
|
||||
|
||||
| Variable | Description | Example/Default Value |
|
||||
| :------------- |:------------------------| -----:|
|
||||
| `PUID` |Runtime UID override, set to `0` to run as root. | `20211` |
|
||||
@@ -127,8 +130,3 @@ You can read or watch several [community configuration guides](https://docs.neta
|
||||
|
||||
| [](https://github.com/sponsors/jokob-sk) | [](https://www.buymeacoffee.com/jokobsk) |
|
||||
| --- | --- |
|
||||
|
||||
- Bitcoin: `1N8tupjeCK12qRVU2XrV17WvKK7LCawyZM`
|
||||
- Ethereum: `0x6e2749Cb42F4411bc98501406BdcD82244e3f9C7`
|
||||
|
||||
> 📧 Email me at [support@netalertx.com](mailto:support@netalertx.com?subject=NetAlertX Donations) if you want to get in touch or if I should add other sponsorship platforms.
|
||||
+11
-2
@@ -82,9 +82,18 @@ volumes:
|
||||
10. Navigate to `<Synology URL>:20211` (or your custom port).
|
||||
11. Read the [Subnets](./SUBNETS.md) and [Plugins](./PLUGINS_OVERVIEW.md) docs to complete your setup.
|
||||
|
||||
## Solving permission issues
|
||||
## Solving permission issues (2 devices visible)
|
||||
|
||||
See also the [Permission overview guide](./FILE_PERMISSIONS.md).
|
||||
Some Synology setups don't support `--cap-add` properly. This usually results in seeing only 2 devices and the following error shows when running `ARPSCAN`:
|
||||
|
||||
```bash
|
||||
You don't have permission to perform this capture on that device
|
||||
(socket: Operation not permitted)
|
||||
```
|
||||
|
||||
To fix this you might need to set the container as ptiviledged `privileged: true` and run as root by setting a custom `PUID` and `PGID`.
|
||||
|
||||
See [running as root](./FILE_PERMISSIONS.md) for more details.
|
||||
|
||||
### Configuring the permissions via SSH
|
||||
|
||||
|
||||
Reference in new issue
Block a user