Applies to Platform: EndianOS 6.x
Last update: 22 Apr 2026
An important feature for the Endian platform in 6.x is the addition of Docker to allow users to run containers locally on an Endian appliance. Docker solves one of the most common frustrations in software: making sure applications work reliably everywhere. By packaging software and its dependencies into portable containers, Docker removes the guesswork from setting up and sharing software environments. This article will outline the common commands that can be used to troubleshoot Docker issues.
Products Not Supported
-
Endian Edge V - due to limited resources, this product does not support Docker
Find the Name or ID of a Container
In order to interact with Docker, you will need the name or ID of the container you are interested in getting information about. The easiest way to do this is to use the command below to list the running containers and find the name or ID of the specific container.
root@endian~#: docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e3dd5c3a11f8 nginx "/docker-entrypoint.…" About a minute ago Up About a minute 0.0.0.0:8080-80/tcp hungry_burnell
Check Logs of a Container
You can run the following command to view the most recent logs of a running container. This can be useful to help find more detailed items like configuration or permission based issues.
root@endian~#: docker logs [container name or ID]
Check Networking of a Container
When your containers can’t communicate with each other, you need to test the network setup. Containers running on the same Docker network should be able to reach each other by container name. Alternatively, you can check Internet connectivity as well.
root@endian~#: docker exec -it [container name or ID] /bin/sh
From the container shell, you can typically run common Linux networking commands like ping or curl.
Ping (Connectivity, Latency, Packet Loss)
#: ping [ip address or FQDN]
Curl (Layer 7 Connectivity, Server Port Accessibility, Speed Test)
#: curl [ip address or FQDN]
Check Resource Usage of Containers
You can check resource allocation for one or more containers by using the command below. This command will show you the CPU, memory, network and block I/O for all the running containers. If one or more containers are using too much resources, you should try to optimize or limit their usage or stop the container until another solution can be found.
root@endian~#: docker stats
Clean Up Container Resources
Sometimes you can build up unused images, containers or volumes and it can be helpful to clean them up using the commands below
Clean up unused containers, images and volumes:
root@endian~#: docker system prune -a
Clean up only unused volumes:
root@endian~#: docker volume prune
Comments