Docker Swarm API

Docker Swarm API The Docker Swarm API is mostly compatible with the Docker Remote API. This document is an overview of the differences between the Swarm API and the Docker Remote API. Missing endpoints Some endpoints have not yet been implemented and will return a 404 error. POST "/images/create" : "docker import" flow not implement Endpoints which behave differently Endpoint Differences GET "/containers/{name:.*}/json" New field Node added: "Node": { "Id": "ODAI:IC6Q:MSBL:TPB5:HIEE:6IK

PowerShell DSC Usage

Using PowerShell DSC Windows PowerShell Desired State Configuration (DSC) is a configuration management tool that extends the existing functionality of Windows PowerShell. DSC uses a declarative syntax to define the state in which a target should be configured. More information about PowerShell DSC can be found at http://technet.microsoft.com/en-us/library/dn249912.aspx. Requirements To use this guide you’ll need a Windows host with PowerShell v4.0 or newer. The included DSC configuration scrip

OverlayFS storage in practice

Docker and OverlayFS in practice OverlayFS is a modern union filesystem that is similar to AUFS. In comparison to AUFS, OverlayFS: has a simpler design has been in the mainline Linux kernel since version 3.18 is potentially faster As a result, OverlayFS is rapidly gaining popularity in the Docker community and is seen by many as a natural successor to AUFS. As promising as OverlayFS is, it is still relatively young. Therefore caution should be taken before using it in production Docker enviro

docker port

port Usage: docker port [OPTIONS] CONTAINER [PRIVATE_PORT[/PROTO]] List port mappings for the CONTAINER, or lookup the public-facing port that is NAT-ed to the PRIVATE_PORT --help Print usage You can find out all the ports mapped by not specifying a PRIVATE_PORT, or just a specific mapping: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b650456536c7 busybo

Customize the docker0 bridge

Customize the docker0 bridge The information in this section explains how to customize the Docker default bridge. This is a bridge network named bridge created automatically when you install Docker. Note: The Docker networks feature allows you to create user-defined networks in addition to the default bridge network. By default, the Docker server creates and configures the host system’s docker0 interface as an Ethernet bridge inside the Linux kernel that can pass packets back and forth between

docker-compose config

config Usage: config [options] Options: -q, --quiet Only validate the configuration, don't print anything. --services Print the service names, one per line. Validate and view the compose file.

Journald logging driver

Journald logging driver The journald logging driver sends container logs to the systemd journal. Log entries can be retrieved using the journalctl command, through use of the journal API, or using the docker logs command. In addition to the text of the log message itself, the journald log driver stores the following metadata in the journal with each message: Field Description CONTAINER_ID The container ID truncated to 12 characters. CONTAINER_ID_FULL The full 64-character container ID. CONTAINE

Runtime metrics

Runtime metrics Docker stats You can use the docker stats command to live stream a container’s runtime metrics. The command supports CPU, memory usage, memory limit, and network IO metrics. The following is a sample output from the docker stats command $ docker stats redis1 redis2 CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O redis1 0.07% 796 KB / 64 MB 1.21% 788 B / 648 B 3.5

Remote API v1.19

Docker Remote API v1.19 1. Brief introduction The Remote API has replaced rcli. The daemon listens on unix:///var/run/docker.sock but you can Bind Docker to another host/port or a Unix socket. The API tends to be REST. However, for some complex commands, like attach or pull, the HTTP connection is hijacked to transport stdout, stdin and stderr. When the client API version is newer than the daemon’s, these calls return an HTTP 400 Bad Request error message. 2. Endpoints 2.1 Containers List con

Play in a content trust sandbox

Play in a content trust sandbox This page explains how to set up and use a sandbox for experimenting with trust. The sandbox allows you to configure and try trust operations locally without impacting your production images. Before working through this sandbox, you should have read through the trust overview. Prerequisites These instructions assume you are running in Linux or Mac OS X. You can run this sandbox on a local machine or on a virtual machine. You will need to have sudo privileges on y