This library allows you to interact with Docker Remote API endpoints in your .NET applications.

It is fully asynchronous, designed to be non-blocking and object-oriented way to interact with your Docker daemon programmatically.

Version of this package uses SemVer format: MAJOR.MINOR.PATCH. MINOR segment indicates the Docker Remote API version support. For instance v2.124.0 of this library supports Docker Remote APIv1.24. This does not guarantee backwards compatibility as Docker Remote API does not guarantee that either.

MAJOR is reserved for major breaking changes we make to the library itself such as how the calls are made or how authentication is made. PATCH is just for incremental bug fixes or non-breaking feature additions.

You can add this library to your project using NuGet.

Package Manager Console Run the following command in the “Package Manager Console”:

PM> Install-Package Docker.DotNet

Visual Studio Right click to your project in Visual Studio, choose “Manage NuGet Packages” and search for ‘Docker.DotNet’ and click ‘Install’. (see NuGet Gallery.)

.NET Core Command Line Interface Run the following command from your favorite shell or terminal:

dotnet add package Docker.DotNet

Development Builds

If you intend to use development builds of Docker.DotNet and don't want to compile the code yourself you can add the package source below to Visual Studio or your Nuget.Config.

https://ci.appveyor.com/nuget/docker-dotnet-hojfmn6hoed7

You can initialize the client like the following:

usingDocker.DotNet;DockerClientclient=newDockerClientConfiguration(newUri("http://ubuntu-docker.cloudapp.net:4243")).CreateClient();

or to connect to your local Docker for Windows daemon using named pipes or your local Docker for Mac daemon using Unix sockets:

usingDocker.DotNet;DockerClientclient=newDockerClientConfiguration().CreateClient();

For a custom endpoint, you can also pass a named pipe or a Unix socket to the DockerClientConfiguration constructor. For example:

// Default Docker Engine on WindowsusingDocker.DotNet;DockerClientclient=newDockerClientConfiguration(newUri("npipe://./pipe/docker_engine")).CreateClient();// Default Docker Engine on LinuxusingDocker.DotNet;DockerClientclient=newDockerClientConfiguration(newUri("unix:///var/run/docker.sock")).CreateClient();

IList<ContainerListResponse>containers=awaitclient.Containers.ListContainersAsync(newContainersListParameters(){Limit=10,});

The code below pulls fedora/memcached image to your Docker instance using your Docker Hub account. You can anonymously download the image as well by passing null instead of AuthConfig object:

awaitclient.Images.CreateImageAsync(newImagesCreateParameters{FromImage="fedora/memcached",Tag="alpha",},newAuthConfig{Email="[email protected]",Username="test",Password="pa$$w0rd"},newProgress<JSONMessage>());

The following code will create a new container of the previously fetched image.

awaitclient.Containers.CreateContainerAsync(newCreateContainerParameters(){Image="fedora/memcached",HostConfig=newHostConfig(){DNS=new[]{"8.8.8.8","8.8.4.4"}}});

The following code will start the created container.

awaitclient.Containers.StartContainerAsync("39e3317fd258",newContainerStartParameters());

The following code will stop a running container.

Note: WaitBeforeKillSeconds field is of type uint? which means optional. This code will wait 30 seconds before killing it. If you like to cancel the waiting, you can use the CancellationToken parameter.

varstopped=awaitclient.Containers.StopContainerAsync("39e3317fd258",newContainerStopParameters{WaitBeforeKillSeconds=30},CancellationToken.None);

Some Docker API endpoints are designed to return stream responses. For example Monitoring Docker events continuously streams the status in a format like :

{"status":"create","id":"dfdf82bd3881","from":"base:latest","time":1374067924}{"status":"start","id":"dfdf82bd3881","from":"base:latest","time":1374067924}{"status":"stop","id":"dfdf82bd3881","from":"base:latest","time":1374067966}{"status":"destroy","id":"dfdf82bd3881","from":"base:latest","time":1374067970} ...

To obtain this stream you can use:

CancellationTokenSourcecancellation=newCancellationTokenSource();Streamstream=awaitclient.System.MonitorEventsAsync(newContainerEventsParameters(),newProgress<JSONMessage>(),cancellation.Token);// Initialize a StreamReader...

You can cancel streaming using the CancellationToken. On the other hand, if you wish to continuously stream, you can simply pass CancellationToken.None.

If you are running Docker with TLS (HTTPS), you can authenticate to the Docker instance using the Docker.DotNet.X509 package. You can get this package from NuGet or by running the following command in the “Package Manager Console”:

PM> Install-Package Docker.DotNet.X509 

Once you add Docker.DotNet.X509 to your project, use CertificateCredentials type:

varcredentials=newCertificateCredentials(newX509Certificate2("CertFile","Password"));varconfig=newDockerClientConfiguration("http://ubuntu-docker.cloudapp.net:4243",credentials);DockerClientclient=config.CreateClient();

If you don't want to authenticate you can omit the credentials parameter, which defaults to an AnonymousCredentials instance.

The CertFile in the example above should be a .pfx file (PKCS12 format), if you have .pem formatted certificates which Docker normally uses you can either convert it programmatically or use openssl tool to generate a .pfx:

openssl pkcs12 -export -inkey key.pem -in cert.pem -out key.pfx 

(Here, your private key is key.pem, public key is cert.pem and output file is named key.pfx.) This will prompt a password for PFX file and then you can use this PFX file on Windows. If the certificate is self-signed, your application may reject the server certificate, in this case you might want to disable server certificate validation:

//// There are two options to do this.//// You can do this globally for all certificates:ServicePointManager.ServerCertificateValidationCallback+=(o,c,ch,er)=>true;// Or you can do this on a credential by credential basis:varcreds=newCertificateCredentials(...);creds.ServerCertificateValidationCallback+=(o,c,ch,er)=>true;

If the Docker instance is secured with Basic HTTP Authentication, you can use the Docker.DotNet.BasicAuth package. Get this package from NuGet or by running the following command in the “Package Manager Console”:

PM> Install-Package Docker.DotNet.BasicAuth 

Once you added Docker.DotNet.BasicAuth to your project, use BasicAuthCredentials type:

varcredentials=newBasicAuthCredentials("YOUR_USERNAME","YOUR_PASSWORD");varconfig=newDockerClientConfiguration("tcp://ubuntu-docker.cloudapp.net:4243",credentials);DockerClientclient=config.CreateClient();

BasicAuthCredentials also accepts SecureString for username and password arguments.

By default this client does not specify version number to the API for the requests it makes. However, if you would like to make use of versioning feature of Docker Remote API You can initialize the client like the following.

varconfig=newDockerClientConfiguration(...);DockerClientclient=config.CreateClient(newVersion(1,16));

Here are typical exceptions thrown from the client library:

• DockerApiException is thrown when Docker API responds with a non-success result. Subclasses:
  • DockerContainerNotFoundException
  • DockerImageNotFoundException
• TaskCanceledException is thrown from System.Net.Http.HttpClient library by design. It is not a friendly exception, but it indicates your request has timed out. (default request timeout is 100 seconds.)
  • Long-running methods (e.g. WaitContainerAsync, StopContainerAsync) and methods that return Stream (e.g. CreateImageAsync, GetContainerLogsAsync) have timeout value overridden with infinite timespan by this library.
• ArgumentNullException is thrown when one of the required parameters are missing/empty.
  • Consider reading the Docker Remote API reference and source code of the corresponding method you are going to use in from this library. This way you can easily find out which parameters are required and their format.

Docker.DotNet is a .NET Foundation project.

There are many .NET related projects on GitHub.

• .NET home repo - links to 100s of .NET projects, from Microsoft and the community.
• ASP.NET Core home - the best place to start learning about ASP.NET Core.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.

General .NET OSS discussions: .NET Foundation Discord

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.dotnetfoundation.org.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

Docker.DotNet is licensed under the MIT license.

Copyright (c) .NET Foundation and Contributors