Updated 10. Setting the solution up in ACS Kubernetes (markdown)

10.-Setting-the-solution-up-in-ACS-Kubernetes.md

@@ -310,7 +310,20 @@ Finally you can test the web applications at the URLs told at the end of the scr
 You should be able to run the eShop MVC app like in the following screenshot (using your external IP for the cluster, of course)
 <img src="img/kubernetes/eshop-mvc-web-running-on-kubernetes.png">
 
+## Error "Service 'xxxxx' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder123456789/obj/Docker/publish: no such file or directory"
+
+This error means that the project `xxxxx` is not published in their `obj/Docker/publish` folder. Please publish the project first. The easiest way to do it is using the `build-bits` scripts (i.e. `cli-windows/build-bits.ps1`) to rebuild and republish all the projects (or you can also pas the `$buildBits true` to the `deploy.ps1` script). But if you want to publish only one project:
+
+```
+cd src/path/to/csproj
+dotnet restore
+dotnet publish -o obj/Docker/publish
+```
+
+Check that there is no error and the `obj/Docker/publish` folder exists and has the project published.
+
 ## Issues when deploying to Kubernetes in ACS
+
 Sometimes you might have an issue when deploying and some pods might have not be deployed right the first time.
 You can check that out by reviewing the deployments in the Kubernetes dashboard.
 If any of the pods had any issue, you might see like it has 0 (CERO) instances.