From 74d474ccf3ac5b561a8cf7c8a51c116acd6d9ec2 Mon Sep 17 00:00:00 2001 From: Korbs Date: Sun, 23 Feb 2025 17:37:37 -0500 Subject: [PATCH] Update FAQ --- README.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/README.md b/README.md index ac8407f..edf4fea 100755 --- a/README.md +++ b/README.md @@ -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.