docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.2-windowsservercore-ltsc2019
- 4.7.2-windowsservercore-ltsc2019, 4.7.2, latest (4.7.2-windowsservercore-ltsc2019/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.2-windowsservercore-1803
- 4.7.2-windowsservercore-1803, 4.7.2, latest (4.7.2-windowsservercore-1803/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.2-windowsservercore-1709
- 4.7.2-windowsservercore-1709, 4.7.2, latest (4.7.2-windowsservercore-1709/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.1-windowsservercore-1709
- 4.7.1-windowsservercore-1709, 4.7.1 (4.7.1-windowsservercore-1709/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.2-windowsservercore-ltsc2016
- 4.7.2-windowsservercore-ltsc2016, 4.7.2, latest (4.7.2-windowsservercore-ltsc2016/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7.1-windowsservercore-ltsc2016
- 4.7.1-windowsservercore-ltsc2016, 4.7.1 (4.7.1-windowsservercore-ltsc2016/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.7-windowsservercore-ltsc2016
- 4.7-windowsservercore-ltsc2016, 4.7 (4.7-windowsservercore-ltsc2016/runtime/Dockerfile)
docker pull mcr.microsoft.com/dotnet/framework/wcf:4.6.2-windowsservercore-ltsc2016
- 4.6.2-windowsservercore-ltsc2016, 4.6.2 (4.6.2-windowsservercore-ltsc2016/runtime/Dockerfile)
This image is uploaded to the microsoft/wcf docker hub repo with the information of the supported specific tags.
The Windows Communication Foundation (WCF) is a framework for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application.
FROM microsoft/wcf
WORKDIR WcfService
RUN powershell -NoProfile -Command \
Import-module IISAdministration; \
New-IISSite -Name "WcfService" -PhysicalPath C:\WcfService -BindingInformation "*:83:"
EXPOSE 83
COPY content/ .
You can then build and run the Docker image:
$ docker build -t wcfserviceimage .
$ docker run -d -p 83:83 --name my-wcfservice wcfserviceimage
There is no need to specify an ENTRYPOINT in your Dockerfile since an entrypoint application is already specified that monitors the status of the IIS World Wide Web Publishing Service (W3SVC).
For windows version 1803 or higher, you can connect to the running container using 'http://localhost:83/<wcfservice.svc>` in the example shown.
For windows versions prior to 1803, you cannot use http://localhost to browse your site from the container host. This is because of a known behavior in WinNAT for those versions which requires you to use the IP address of the container.
Once the container starts, you'll need to finds its IP address so that you can connect to your running container from a browser. You use the docker inspect command to do that:
docker inspect -f "{{ .NetworkSettings.Networks.nat.IPAddress }}" my-wcfservice
You will see an output similar to this:
172.28.103.001
You can connect to the running container using the IP address and configured port, http://172.28.103.001:83/<wcfservice.svc> in the example shown.
For a comprehensive tutorial on running an WCF service in a container, check out WCF service samples in container
This image has been tested on Docker Versions 1.12.2-cs2-ws-beta or higher.
MICROSOFT SOFTWARE SUPPLEMENTAL LICENSE TERMS
CONTAINER OS IMAGE
Microsoft Corporation (or based on where you live, one of its affiliates) (referenced as "us," "we," or "Microsoft") licenses this Container OS Image supplement to you ("Supplement"). You are licensed to use this Supplement in conjunction with the underlying host operating system software ("Host Software") solely to assist running the containers feature in the Host Software. The Host Software license terms apply to your use of the Supplement. You may not use it if you do not have a license for the Host Software. You may use this Supplement with each validly licensed copy of the Host Software.
If you have any issues or concerns, reach out to us through a GitHub issue.