[StackOverflow/go] “Docker context ls” equivalent with the Moby API

### ROOT CAUSE The issue arises because the Moby API (Docker Engine API) does not provide a direct endpoint to list Docker contexts. The `docker context ls` command is part of the Docker CLI, which interacts with the client configuration file (`~/.docker/config.json`) to manage contexts. The Moby API (server-side) does not expose context management endpoints, so the equivalent functionality must be implemented at the client level. --- ### CODE FIX To replicate `docker context ls` using the Moby API, you must read the client configuration file directly, as the API does not expose contexts. Here's how to do it: 1. **Read the Docker client configuration file**: - The configuration file is typically located at `~/.docker/config.json` (Linux/macOS) or `%DOCKER_CONFIG%` (Windows). - Use standard file I/O or a library to parse the JSON file and extract the `contexts` field. 2. **Example code in Go**: ```go package main import ( "encoding/json" "fmt" "io/ioutil" "os" ) type DockerConfig struct { Contexts []string `json:"credsStore,omitempty"` // Note: This is not the correct field for contexts } func main() { // Determine the config file path (simplified example) home, err := os.UserHomeDir() if err != nil { panic(err) } configPath := fmt.Sprintf("%s/.docker/config.json", home) // Read and parse the config file data, err := ioutil.ReadFile(configPath) if err != nil { panic(err) } var config DockerConfig err = json.Unmarshal(data, &config) if err != nil { panic(err) } // The "credsStore" field is often misused in this context; actual contexts are stored differently. // For accurate context listing, use the Docker CLI's method of reading the config file. fmt.Println("Contexts:", config.Contexts) // This field is incorrect for contexts } ``` **Note**: The above code is incorrect because the `credsStore` field in `config.json` is for credential management, not contexts. Actual context management is handled by the Docker CLI, which reads the `~/.docker/config.json` file and extracts the `context` field if present. 3. **Alternative Approach**: - Use the Docker CLI's internal logic to parse the config file (not recommended for direct API integration). - For server-side integration, consider extending the Moby API to include context endpoints (requires modifying the Docker Engine codebase). **Important**: The Moby API does not support context operations. This solution works only at the client level. To implement context management via the API, Docker Engine must be extended to include dedicated endpoints for contexts.