Korbs/Netweak-Agent-Docker
Korbs/Netweak-Agent-Docker
1
Fork 0
Code Issues Pull requests Activity

Update FAQ

Browse source
This commit is contained in:
Korbs 2025-02-23 17:37:37 -05:00
parent 27b906a70c
commit 74d474ccf3
Signed by: Korbs
SSH key fingerprint: SHA256:Q0b0KraMldpAO9oKa+w+gcsXsOTykQ4UkAKn0ByGn5U
1 changed files with 0 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -97,23 +97,14 @@ SudoVanilla does not have access to any Docker containers you run on your server
This depends on how Docker is setup, I've not yet looked into correcting this behavior.
**CPU information is wrong, why is this?**
The CPU may show up as "N/A" on certain machines. A real example is a Mac Mini M2 running Asahi Linux. If you don't want it to show up as "N/A" anymore, switch to the custom Docker image by adding `-custom` before the tag in the image name. The custom build will modify the Agent file to show the CPU model as "Docker Engine".
`oci.registry.sudovanilla.org/netweak-agent-custom:amd64`
**Why does it say I'm running Debian? I'm not.**
This Docker Image is based on slim edition of Debian 12. When the Netweak agent runs in this Docker Image, it will detect this and assume you're using Debian 12. This is expected behavior.
https://ark.sudovanilla.org/Korbs/-/packages/container/debian-slim/amd64
**Is this an official Docker Image for Netweak?**
No, SudoVanilla is not affiliated with Netweak in any way. This is NOT an official Docker image. SudoVanilla is only an enterprise customer of Netweak and wanted to monitor other non-Linux servers.
**How do I uninstall the agent?**
In Netweak, skip the uninstall instructions and just delete the server.