{
    "content": "<h1>Introduction to the <a href=\"..\/DOCKER-ENGINE-API\/\">DOCKER-ENGINE-API<\/a><\/h1><p>The <a href=\"..\/DOCKER-ENGINE-API\/\">DOCKER-ENGINE-API<\/a> is a comprehensive <a href=\"..\/REST-API\/\">REST-API<\/a> that enables developers to interact directly with the <a href=\"..\/DOCKER-DAEMON\/\">DOCKER-DAEMON<\/a>. This interface is the underlying mechanism used by the <a href=\"..\/DOCKER-CLI\/\">DOCKER-CLI<\/a> to execute commands. By making <a href=\"..\/HTTP\/\">HTTP<\/a> requests to the API, users can programmatically manage the lifecycle of <a href=\"..\/CONTAINERS\/\">CONTAINERS<\/a>, manage <a href=\"..\/IMAGES\/\">IMAGES<\/a>, and orchestrate <a href=\"..\/NETWORKS\/\">NETWORKS<\/a> and <a href=\"..\/VOLUMES\/\">VOLUMES<\/a>.<\/p><p>Accessing the <a href=\"..\/DOCKER-ENGINE-API\/\">DOCKER-ENGINE-API<\/a> is typically done through a <a href=\"..\/UNIX-SOCKET\/\">UNIX-SOCKET<\/a> located at \/var\/run\/docker.sock on <a href=\"..\/LINUX\/\">LINUX<\/a> systems. For remote management, the API can be exposed over a <a href=\"..\/TCP\/\">TCP<\/a> port, though it is highly recommended to secure these connections using <a href=\"..\/TLS\/\">TLS<\/a> to prevent unauthorized access. The API uses standard <a href=\"..\/JSON\/\">JSON<\/a> for request and response bodies, making it compatible with almost any modern programming language.<\/p><p>To simplify integration, <a href=\"..\/DOCKER\/\">DOCKER<\/a> provides official <a href=\"..\/SDK\/\">SDK<\/a> packages for <a href=\"..\/GO\/\">GO<\/a> and <a href=\"..\/PYTHON\/\">PYTHON<\/a>. These libraries wrap the <a href=\"..\/REST-API\/\">REST-API<\/a> endpoints into native function calls, handling details like connection pooling and serialization. Detailed specifications for every endpoint, including versioning history, are maintained in the <a href=\"https:\/\/docs.docker.com\/engine\/api\/\">Docker API Reference<\/a>.<\/p><ul><li><a href=\"..\/DOCKER-COMPOSE\/\">DOCKER-COMPOSE<\/a><\/li><li><a href=\"..\/KUBERNETES\/\">KUBERNETES<\/a><\/li><li><a href=\"..\/CONTAINERD\/\">CONTAINERD<\/a><\/li><li><a href=\"..\/MICROSERVICES\/\">MICROSERVICES<\/a><\/li><\/ul>",
    "tags": [
        "docker",
        "api",
        "rest",
        "containers",
        "devops",
        "automation",
        "infrastructure",
        "backend",
        "cloud",
        "virtualization"
    ]
}