Example of a simple Sitecore solution configured to be deployed, during development, to a docker instance.
As Sitecore does not provide a set of docker images you need to first build them using the instructions in the sitecore-docker repo.
- 
Open the solution in Visual Studio and invoke the publish operation on the SampleSite project. This will build the project and output its content to the
.artifactsfolder. - 
Create the folders
.logs\sitecoreand.logs\xconnectin the root of the solution. - 
Invoke
docker-compose up -d. This will bring Sitecore up, the files from the.artifactsfolder are copied to the webroot of Sitecore. Logs are output in the.logsfolder. - 
Sitecore should be available under
http://sitecore/. - 
If you are using Unicorn, you don't need to change the default serialization folder. Serialized items are picked from the
serializationfolder. Open thehttp://sitecore/unicorn.aspxpage and either serialize or sync. - 
When you no longer need Sitecore running, you can do
docker-compose stopto stop all the containers, but maintain their state. - 
If at any point you need to remove the Sitecore instance simply do a
docker-compose down. You can always deploy again from scratch invokingdocker-compose up -dagain. 
- Debugging is not yet available
 - Windows containers are quite resource intensive. Adjust the cpu_count and memory values in the 
docker-compose.ymlfile if necessary. Eventually SOLR and MSSQL should be moved to Linux containers. - Sitecore Rocks is not enabled by default. You need to copy the files to the root of sitecore. You could temporarily place them in the 
.artifactsfolder for them to get copied to the site root.