Here is how to resolve this depending on what you want to achieve: ### Option 1: You want to go back to your original Docker setup If you prefer to use your native Docker installation and stop using Colima, switch your context back to `default`: 1. **Switch context:** ```bash docker context use default ``` 2. **Ensure the native service is running:** ```bash sudo systemctl start docker ``` 3. **Verify:** ```bash docker ps ``` *If your containers appear, you are back to your original setup.* ### Option 2: You want to keep using Colima If you intend to use Colima, you need to understand that **Colima does not share the same storage as your native Docker.** Your old containers are still sitting in `/var/lib/docker` (managed by the system Docker), while Colima is looking at its own virtual disk. If you want to use Colima, you should stop the system Docker to avoid conflicts: 1. **Stop the system Docker:** ```bash sudo systemctl stop docker sudo systemctl disable docker ``` 2. **Restart Colima:** ```bash colima stop colima start ``` 3. **Note:** You will need to re-pull your images or rebuild your containers within the Colima environment, as they are not shared between the two runtimes. --- ### 1. Check which Docker context is active Colima creates a specific Docker context. If your terminal is pointed at the wrong one, it won't be able to "see" your existing containers. Run this command to see your contexts: ```bash docker context ls ``` * Look for a context named `colima`. * If you want to go back to your original setup, switch back to the default: ```bash docker context use default ``` ### 2. Check the Docker Socket Colima usually sets the `DOCKER_HOST` environment variable to point to its own socket. Check if this variable is set: ```bash echo $DOCKER_HOST ``` If it returns something like `unix:///home/user/.colima/default/docker.sock`, that is why your native Docker commands aren't working. You can unset it for the current session: ```bash unset DOCKER_HOST ``` ### 3. Are you running both simultaneously? If you have the native Docker Engine (installed via `apt` or `dnf`) running as a system service, it might be fighting with Colima for the default socket (`/var/run/docker.sock`). * **If you want to use the native Docker Engine:** Stop Colima and disable the service. ```bash colima stop sudo systemctl stop docker sudo systemctl start docker ``` * **If you want to use Colima:** Stop the native Docker service so it doesn't interfere. ```bash sudo systemctl stop docker sudo systemctl disable docker colima start ``` ### 4. Verify the status After switching contexts or unsetting the environment variable, try running: ```bash docker ps ``` D 26.09.26

• Home
• Notebook
• Contact us

• Privacy Statement
• 

Copyleft ☠ 2026