🛠 Troubleshooting

This guide provides various commands and techniques to diagnose and troubleshoot common issues with Anteon Self-Hosted when deployed via Docker Compose or Kubernetes.

🔍 Troubleshooting Docker Compose Deployment​

tip

You can use a TUI tool like Ducker to easily analyze the containers.

Inspect Docker Containers​

To list all running containers:

docker ps

To inspect a specific container for detailed information:

docker inspect <container_id>

docker exec -it <container_id> /bin/sh

Check Logs​

To view the logs for all services running under Docker Compose:

docker compose logs

docker compose logs selfhosted-frontend-1

Restarting Services​

If a service is not responding, you can restart it using:

docker compose restart <service_name>

Verify Network Connectivity​

Ensure that all services are properly connected to the Docker network:

docker network inspect <network_name>

You can ping between containers to verify connectivity:

docker exec -it <container_id> ping <target_container_id_or_name>

Checking Resource Usage​

To check CPU and memory usage of the containers:

docker stats

☸️ Troubleshooting Kubernetes Deployment​

tip

You can use a TUI tool like kubetui to easily analyze the containers.

Check Pod Status​

To check the status of all Pods in the namespace:

kubectl get pods -n <namespace>

kubectl describe pod <pod_name> -n <namespace>

View Pod Logs​

To view logs for a specific container within a Pod:

kubectl logs <pod_name> -n <namespace> -c <container_name>

If the Pod has multiple containers and you omit -c <container_name>, logs from the first container will be shown.

Restarting Pods​

To delete and restart a Pod (which forces Kubernetes to create a new one):

kubectl delete pod <pod_name> -n <namespace>

Check Service Endpoints​

To verify that a service is correctly routing traffic:

kubectl get endpoints <service_name> -n <namespace>

This will show which Pods are connected to the service.

Inspecting Events​

To check for any events that might indicate issues:

kubectl get events -n <namespace>

Debugging with a Temporary Pod​

You can create a temporary Pod to run debugging commands within the Kubernetes cluster:

kubectl run -i --tty --rm debug-pod --image=alpine -- sh

From within this Pod, you can ping services, check DNS resolution, etc.

Monitoring Resource Usage​

To view resource usage across the cluster:

kubectl top nodes

For detailed resource usage per Pod:

kubectl top pods -n <namespace>