Important
Unfortunately, there has been no further development or bug fixes in Docker.DotNet for some time now, and the repository appears inactive. Reaching the current maintainer is challenging. I understand that priorities shift, and maintaining an open-source project is time-consuming and exhausting. As maintainers, we often cannot dedicate the necessary time. Over the past months—and even years—I have frequently offered my help.
Docker.DotNet is an important upstream dependency for Testcontainers for .NET and many other developers. It would be unfortunate for this valuable work not to continue. Therefore, I have decided to fork the repository to focus on essential fixes, improvements, and updates for the Docker Engine API. I am also accepting further contributions and remaining PRs from the upstream repository.
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 API v1.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.
You can initialize the client like the following:
using Docker.DotNet;
DockerClient client = new DockerClientConfiguration(
new Uri("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:
using Docker.DotNet;
DockerClient client = new DockerClientConfiguration()
.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 Windows
using Docker.DotNet;
DockerClient client = new DockerClientConfiguration(
new Uri("npipe://./pipe/docker_engine"))
.CreateClient();
// Default Docker Engine on Linux
using Docker.DotNet;
DockerClient client = new DockerClientConfiguration(
new Uri("unix:///var/run/docker.sock"))
.CreateClient();IList<ContainerListResponse> containers = await client.Containers.ListContainersAsync(
new ContainersListParameters(){
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:
await client.Images.CreateImageAsync(
new ImagesCreateParameters
{
FromImage = "fedora/memcached",
Tag = "alpha",
},
new AuthConfig
{
Email = "[email protected]",
Username = "test",
Password = "pa$$w0rd"
},
new Progress<JSONMessage>());The following code will create a new container of the previously fetched image.
await client.Containers.CreateContainerAsync(new CreateContainerParameters()
{
Image = "fedora/memcached",
HostConfig = new HostConfig()
{
DNS = new[] { "8.8.8.8", "8.8.4.4" }
}
});The following code will start the created container.
await client.Containers.StartContainerAsync(
"39e3317fd258",
new ContainerStartParameters()
);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.
var stopped = await client.Containers.StopContainerAsync(
"39e3317fd258",
new ContainerStopParameters
{
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:
CancellationTokenSource cancellation = new CancellationTokenSource();
Stream stream = await client.System.MonitorEventsAsync(new ContainerEventsParameters(), new Progress<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:
var credentials = new CertificateCredentials (new X509Certificate2 ("CertFile", "Password"));
var config = new DockerClientConfiguration("http://ubuntu-docker.cloudapp.net:4243", credentials);
DockerClient client = 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:
var creds = new CertificateCredentials(...);
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:
var credentials = new BasicAuthCredentials ("YOUR_USERNAME", "YOUR_PASSWORD");
var config = new DockerClientConfiguration("tcp://ubuntu-docker.cloudapp.net:4243", credentials);
DockerClient client = 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.
var config = new DockerClientConfiguration(...);
DockerClient client = config.CreateClient(new Version(1, 16));Here are typical exceptions thrown from the client library:
DockerApiExceptionis thrown when Docker API responds with a non-success result. Subclasses:DockerContainerNotFoundExceptionDockerImageNotFoundException
TaskCanceledExceptionis thrown fromSystem.Net.Http.HttpClientlibrary 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.
- Long-running methods (e.g.
ArgumentNullExceptionis 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