Closed stephenvselvaraj closed 3 years ago
Are you sure you have Docker running on your system, this is commonly seen when Docker isn't running?
Hi Rob,
Thanks for the quick reply. Yes, Docker is running and please the screen shot below. Thanks
@.***D758D8.369B3300]
From: Rob Earlam @.> Sent: 04 June 2021 00:07 To: Sitecore/MVP-Site @.> Cc: stephenvselvaraj @.>; Author @.> Subject: Re: [Sitecore/MVP-Site] docker.errors.DockerException: Error while fetching server API version: (#24)
Are you sure you have Docker running on your system, this is commonly seen when Docker isn't running?
https://stackoverflow.com/a/64953813
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sitecore/MVP-Site/issues/24#issuecomment-854242408, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUISMWSW2FGOQ4436JV5XK3TRADJLANCNFSM46BUDVJQ.
EMAIL DISCLAIMER: This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of 3chillies Limited unless otherwise stated. Registered office: 3chillies Limited, Unit 6, Beacontree Plaza, Gillette Way, Reading Berkshire RG2 0BS, United Kingdom.
Those error's dont tell enough really, can you post the full console output?
Someone on Sitecore Slack had this same issue the other day. Reportedly solved it like this:
"The issue is the UpdateEnvCompose.ps1 script changed the encoding of .env. Solved the issue by creating a new file and pasting the values over (edited) "
Hi Rob,
This POC is for a Green field Project going to kick off coming Monday, I have proposed in the meeting containerisation and its importance. This is the only chance and time I need to address this issue. Your video demonstration are different level and highly valuable. Please help me on this.
Following are the full console output
PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master> .\up.ps1 Tool 'sitecore.cli' (version '2.0.0') was restored. Available commands: sitecore
Restore was successful. solr uses an image, skipping redis uses an image, skipping traefik uses an image, skipping Building dotnetsdk Sending build context to Docker daemon 3.584kB Step 1/11 : ARG BUILD_IMAGE Step 2/11 : ARG NETCORE_BUILD_IMAGE Step 3/11 : FROM ${NETCORE_BUILD_IMAGE} as netcore-sdk ---> a22d08c154c3 Step 4/11 : FROM ${BUILD_IMAGE} ---> 30f28c4f7703 Step 5/11 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 890e3e98ba44 Step 6/11 : ENV NUGET_VERSION 5.6.0 ---> Using cache ---> a0d78f79b7d0 Step 7/11 : RUN Invoke-WebRequest https://dist.nuget.org/win-x86-commandline/v$env:NUGET_VERSION/nuget.exe -UseBasicParsing -OutFile "$env:ProgramFiles\NuGet\nuget.exe" ---> Using cache ---> e31fda3b3515 Step 8/11 : COPY --from=netcore-sdk ["/Program Files/dotnet/", "/Program Files/dotnet/"] ---> Using cache ---> c920b21d0aed Step 9/11 : ENV DOTNET_RUNNING_IN_CONTAINER=true DOTNET_USE_POLLING_FILE_WATCHER=true NUGET_XMLDOC_MODE=skip ---> Using cache ---> 6051940e4e85 Step 10/11 : RUN $path = ${Env:PATH} + ';C:\Program Files\dotnet\;'; setx /M PATH $path ---> Using cache ---> 5324b86b03ce Step 11/11 : RUN dotnet help | out-null ---> Using cache ---> bfc92bae8713 Successfully built bfc92bae8713 Successfully tagged mvp-dotnetsdk:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building mssql Sending build context to Docker daemon 2.048kB Step 1/7 : ARG BASE_IMAGE Step 2/7 : ARG JSS_RESOURCES_IMAGE Step 3/7 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 4/7 : FROM ${BASE_IMAGE} ---> 3a88c1706b88 Step 5/7 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 7e7a43eb8156 Step 6/7 : COPY --from=jss_resources C:\module\db C:\jss_data ---> Using cache ---> 60959acbc049 Step 7/7 : RUN C:\DeployDatabases.ps1 -ResourcesDirectory C:\jss_data; Remove-Item -Path C:\jss_data -Recurse -Force; ---> Using cache ---> 386c0b4429e4 Successfully built 386c0b4429e4 Successfully tagged mvp-mssql:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building solr-init Sending build context to Docker daemon 2.048kB Step 1/3 : ARG BASE_IMAGE Step 2/3 : FROM ${BASE_IMAGE} ---> 111212b65b32 Step 3/3 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 6268f32aec3c Successfully built 6268f32aec3c Successfully tagged mvp-solr-init:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building solutionBuildOutput Sending build context to Docker daemon 30.5MB Step 1/23 : ARG BASE_IMAGE Step 2/23 : ARG BUILD_IMAGE Step 3/23 : FROM ${BUILD_IMAGE} AS nuget-prep ---> bfc92bae8713 Step 4/23 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> f394fc1f4be3 Step 5/23 : COPY .sln nuget.config /nuget/ ---> Using cache ---> 266a3e6b3af0 Step 6/23 : COPY src/ /temp/ ---> Using cache ---> 11ca65f22a2b Step 7/23 : RUN Invoke-Expression 'robocopy C:/temp C:/nuget/src /s /ndl /njh /njs .csproj *.scproj packages.config' ---> Using cache ---> 4237cfadf9ed Step 8/23 : FROM ${BUILD_IMAGE} AS builder ---> bfc92bae8713 Step 9/23 : ARG BUILD_CONFIGURATION ---> Using cache ---> 1fa64f8d748a Step 10/23 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 86068ab2f1a3 Step 11/23 : WORKDIR /build ---> Using cache ---> e136f12e4c84 Step 12/23 : COPY --from=nuget-prep ./nuget ./ ---> Using cache ---> f057b6435c59 Step 13/23 : RUN dotnet restore ---> Using cache ---> 544e3bf10d37 Step 14/23 : COPY src/ ./src/ ---> Using cache ---> a87395df0aaf Step 15/23 : RUN msbuild .\src\Environment\sitecore\Mvp.Environment.Sitecore.csproj /p:Configuration=Release /restore /m /p:DeployOnBuild=true /p:PublishProfile=Local ---> Using cache ---> dc52e35d7c5f Step 16/23 : RUN msbuild .\src\Environment\identity\Mvp.Environment.Identity.csproj /p:Configuration=Release /restore /m /p:DeployOnBuild=true /p:PublishProfile=Local ---> Using cache ---> 4a5b5a23bcd6 Step 17/23 : WORKDIR .\src\Project\MvpSite\rendering\ ---> Using cache ---> dc1758ca6faa Step 18/23 : RUN dotnet publish -c Release -o /build/rendering ---> Using cache ---> 4ceeda0d0316 Step 19/23 : FROM ${BASE_IMAGE} ---> ad675c9cb2d5 Step 20/23 : WORKDIR /artifacts ---> Using cache ---> 1306d4d07af8 Step 21/23 : COPY --from=builder /build/docker/deploy/sitecore ./sitecore/ ---> Using cache ---> b66383587003 Step 22/23 : COPY --from=builder /build/docker/deploy/identity/Config ./identity/Config ---> Using cache ---> 22c39cd8c4ee Step 23/23 : COPY --from=builder /build/rendering ./rendering/ ---> Using cache ---> 68e686d14d67 Successfully built 68e686d14d67 Successfully tagged mvp-solution:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building cd Sending build context to Docker daemon 2.56kB Step 1/15 : ARG BASE_IMAGE Step 2/15 : ARG SOLUTION_IMAGE Step 3/15 : ARG TOOLS_RESOURCES_IMAGE Step 4/15 : ARG JSS_RESOURCES_IMAGE Step 5/15 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 6/15 : FROM ${TOOLS_RESOURCES_IMAGE} as tooling ---> 25d03b8c74d1 Step 7/15 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 8/15 : FROM ${BASE_IMAGE} ---> 3a1378b5e3d9 Step 9/15 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 37439d3b353d Step 10/15 : WORKDIR C:\inetpub\wwwroot ---> Using cache ---> 32868188e6ae Step 11/15 : COPY --from=tooling C:\tools C:\tools ---> Using cache ---> baafb78b3276 Step 12/15 : COPY --from=jss_resources C:\module\cd\content C:\inetpub\wwwroot ---> Using cache ---> c832a80d2380 Step 13/15 : COPY --from=jss_resources C:\module\tools C:\module\tools ---> Using cache ---> 1c6c181f8df8 Step 14/15 : RUN C:\module\tools\Initialize-Content.ps1 -TargetPath C:\inetpub\wwwroot; Remove-Item -Path C:\module -Recurse -Force; ---> Using cache ---> 22b9b4327922 Step 15/15 : COPY --from=solution /artifacts/sitecore/ ./ ---> Using cache ---> 607b7bf56982 Successfully built 607b7bf56982 Successfully tagged mvp-cd:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building id Sending build context to Docker daemon 2.048kB Step 1/8 : ARG BASE_IMAGE Step 2/8 : ARG SOLUTION_IMAGE Step 3/8 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 4/8 : FROM ${BASE_IMAGE} ---> da26fad74a8c Step 5/8 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 5eb42c09b3f2 Step 6/8 : WORKDIR C:\Identity ---> Using cache ---> 8970732729a6 Step 7/8 : COPY --from=solution /artifacts/identity/ ./ ---> Using cache ---> f99ee6df4cbc Step 8/8 : ENTRYPOINT ["dotnet", "Sitecore.IdentityServer.Host.dll"] ---> Using cache ---> af5d60d303f9 Successfully built af5d60d303f9 Successfully tagged mvp-id:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building cm Sending build context to Docker daemon 2.56kB Step 1/18 : ARG BASE_IMAGE Step 2/18 : ARG SOLUTION_IMAGE Step 3/18 : ARG TOOLS_RESOURCES_IMAGE Step 4/18 : ARG DEVEX_RESOURCES_IMAGE Step 5/18 : ARG JSS_RESOURCES_IMAGE Step 6/18 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 7/18 : FROM ${TOOLS_RESOURCES_IMAGE} as tooling ---> 25d03b8c74d1 Step 8/18 : FROM ${DEVEX_RESOURCES_IMAGE} AS devex_resources ---> 96423725498a Step 9/18 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 10/18 : FROM ${BASE_IMAGE} ---> 4719259d16de Step 11/18 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 1dc6457cd443 Step 12/18 : WORKDIR C:\inetpub\wwwroot ---> Using cache ---> 85026e6b9b09 Step 13/18 : COPY --from=tooling C:\tools C:\tools ---> Using cache ---> 1e9e6ce84058 Step 14/18 : COPY --from=devex_resources C:\module\cm\content C:\inetpub\wwwroot ---> Using cache ---> 0bc72ef6b1e8 Step 15/18 : COPY --from=jss_resources C:\module\cm\content C:\inetpub\wwwroot ---> Using cache ---> f6621ec07eac Step 16/18 : COPY --from=jss_resources C:\module\tools C:\module\tools ---> Using cache ---> 283c62ff0712 Step 17/18 : RUN C:\module\tools\Initialize-Content.ps1 -TargetPath C:\inetpub\wwwroot; Remove-Item -Path C:\module -Recurse -Force; ---> Using cache ---> 0ffbf3881465 Step 18/18 : COPY --from=solution /artifacts/sitecore/ ./ ---> Using cache ---> 2de4d9067657 Successfully built 2de4d9067657 Successfully tagged mvp-cm:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building mvp-rendering Sending build context to Docker daemon 2.56kB Step 1/6 : ARG DEBUG_BASE_IMAGE Step 2/6 : ARG RELEASE_BASE_IMAGE Step 3/6 : ARG SOLUTION_IMAGE Step 4/6 : FROM ${DEBUG_BASE_IMAGE} as debug ---> bfc92bae8713 Step 5/6 : WORKDIR /solution/src ---> Using cache ---> 4b977209be5c Step 6/6 : ENTRYPOINT ["dotnet", "watch", "-v", "--project", ".\Project\MvpSite\rendering", "run", "--no-launch-profile"] ---> Using cache ---> 88f3435497e1 Successfully built 88f3435497e1 Successfully tagged mvp-rendering:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Docker Compose is now in the Docker CLI, try docker compose up
mvp-site-master_redis_1 is up-to-date mvp-site-master_mssql_1 is up-to-date mvp-site-master_solr_1 is up-to-date Starting mvp-site-master_solr-init_1 ... Starting mvp-site-master_solr-init_1 ... done mvp-site-master_cd_1 is up-to-date mvp-site-master_cm_1 is up-to-date mvp-rendering is up-to-date Starting mvp-site-master_traefik_1 ... error
ERROR: for mvp-site-master_traefik_1 Cannot start service traefik: failed to create endpoint mvp-site-master_traefik_1 on network nat: failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)
ERROR: for traefik Cannot start service traefik: failed to create endpoint mvp-site-master_traefik_1 on network nat: failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)
ERROR: Encountered errors while bringing up the project.
Waiting for CM to become available...
Invoke-RestMethod: C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master\up.ps1:26:19
Line |
26 | … $status = Invoke-RestMethod "http://localhost:8079/api/http/routers …
| ~~~~~~~~~~~~~
| No connection could be made because the target machine actively refused it.
PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master> docker scan Docker Scan relies upon access to Snyk, a third party provider, do you consent to proceed using Snyk? (y/N) y Usage: docker scan [OPTIONS] IMAGE
A tool to scan your images
Options: --accept-license Accept using a third party scanning provider --dependency-tree Show dependency tree with scan results --exclude-base Exclude base image from vulnerability scanning (requires --file) -f, --file string Dockerfile associated with image, provides more detailed results --group-issues Aggregate duplicated vulnerabilities and group them to a single one (requires --json) --json Output results in JSON format --login Authenticate to the scan provider using an optional token (with --token), or web base token if empty --reject-license Reject using a third party scanning provider --severity string Only report vulnerabilities of provided level or higher (low|medium|high) --token string Authentication token to login to the third party scanning provider --version Display version of the scan plugin "docker scan" requires exactly 1 argument PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master>
From: Rob Earlam @.> Sent: 04 June 2021 06:38 To: Sitecore/MVP-Site @.> Cc: stephenvselvaraj @.>; Author @.> Subject: Re: [Sitecore/MVP-Site] docker.errors.DockerException: Error while fetching server API version: (#24)
Those error's dont tell enough really, can you post the full console output?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sitecore/MVP-Site/issues/24#issuecomment-854373123, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUISMWT2UXB2PCYPCDKD3WTTRBRDXANCNFSM46BUDVJQ.
EMAIL DISCLAIMER: This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of 3chillies Limited unless otherwise stated. Registered office: 3chillies Limited, Unit 6, Beacontree Plaza, Gillette Way, Reading Berkshire RG2 0BS, United Kingdom.
Hi Mark,
Thanks for the update.
The issue is the UpdateEnvCompose.ps1 script changed the encoding of .env. Solved the issue by creating a new file and pasting the values over (edited)
I cant find UpdateEnvCompose.ps1 under the directory. Could you please send me the link?.
@.***D75919.8F361660]
Following are the full console output
PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master> .\up.ps1 Tool 'sitecore.cli' (version '2.0.0') was restored. Available commands: sitecore
Restore was successful. solr uses an image, skipping redis uses an image, skipping traefik uses an image, skipping Building dotnetsdk Sending build context to Docker daemon 3.584kB Step 1/11 : ARG BUILD_IMAGE Step 2/11 : ARG NETCORE_BUILD_IMAGE Step 3/11 : FROM ${NETCORE_BUILD_IMAGE} as netcore-sdk ---> a22d08c154c3 Step 4/11 : FROM ${BUILD_IMAGE} ---> 30f28c4f7703 Step 5/11 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 890e3e98ba44 Step 6/11 : ENV NUGET_VERSION 5.6.0 ---> Using cache ---> a0d78f79b7d0 Step 7/11 : RUN Invoke-WebRequest https://dist.nuget.org/win-x86-commandline/v$env:NUGET_VERSION/nuget.exe -UseBasicParsing -OutFile "$env:ProgramFiles\NuGet\nuget.exe" ---> Using cache ---> e31fda3b3515 Step 8/11 : COPY --from=netcore-sdk ["/Program Files/dotnet/", "/Program Files/dotnet/"] ---> Using cache ---> c920b21d0aed Step 9/11 : ENV DOTNET_RUNNING_IN_CONTAINER=true DOTNET_USE_POLLING_FILE_WATCHER=true NUGET_XMLDOC_MODE=skip ---> Using cache ---> 6051940e4e85 Step 10/11 : RUN $path = ${Env:PATH} + ';C:\Program Files\dotnet\;'; setx /M PATH $path ---> Using cache ---> 5324b86b03ce Step 11/11 : RUN dotnet help | out-null ---> Using cache ---> bfc92bae8713 Successfully built bfc92bae8713 Successfully tagged mvp-dotnetsdk:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building mssql Sending build context to Docker daemon 2.048kB Step 1/7 : ARG BASE_IMAGE Step 2/7 : ARG JSS_RESOURCES_IMAGE Step 3/7 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 4/7 : FROM ${BASE_IMAGE} ---> 3a88c1706b88 Step 5/7 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 7e7a43eb8156 Step 6/7 : COPY --from=jss_resources C:\module\db C:\jss_data ---> Using cache ---> 60959acbc049 Step 7/7 : RUN C:\DeployDatabases.ps1 -ResourcesDirectory C:\jss_data; Remove-Item -Path C:\jss_data -Recurse -Force; ---> Using cache ---> 386c0b4429e4 Successfully built 386c0b4429e4 Successfully tagged mvp-mssql:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building solr-init Sending build context to Docker daemon 2.048kB Step 1/3 : ARG BASE_IMAGE Step 2/3 : FROM ${BASE_IMAGE} ---> 111212b65b32 Step 3/3 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 6268f32aec3c Successfully built 6268f32aec3c Successfully tagged mvp-solr-init:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building solutionBuildOutput Sending build context to Docker daemon 30.5MB Step 1/23 : ARG BASE_IMAGE Step 2/23 : ARG BUILD_IMAGE Step 3/23 : FROM ${BUILD_IMAGE} AS nuget-prep ---> bfc92bae8713 Step 4/23 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> f394fc1f4be3 Step 5/23 : COPY .sln nuget.config /nuget/ ---> Using cache ---> 266a3e6b3af0 Step 6/23 : COPY src/ /temp/ ---> Using cache ---> 11ca65f22a2b Step 7/23 : RUN Invoke-Expression 'robocopy C:/temp C:/nuget/src /s /ndl /njh /njs .csproj *.scproj packages.config' ---> Using cache ---> 4237cfadf9ed Step 8/23 : FROM ${BUILD_IMAGE} AS builder ---> bfc92bae8713 Step 9/23 : ARG BUILD_CONFIGURATION ---> Using cache ---> 1fa64f8d748a Step 10/23 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 86068ab2f1a3 Step 11/23 : WORKDIR /build ---> Using cache ---> e136f12e4c84 Step 12/23 : COPY --from=nuget-prep ./nuget ./ ---> Using cache ---> f057b6435c59 Step 13/23 : RUN dotnet restore ---> Using cache ---> 544e3bf10d37 Step 14/23 : COPY src/ ./src/ ---> Using cache ---> a87395df0aaf Step 15/23 : RUN msbuild .\src\Environment\sitecore\Mvp.Environment.Sitecore.csproj /p:Configuration=Release /restore /m /p:DeployOnBuild=true /p:PublishProfile=Local ---> Using cache ---> dc52e35d7c5f Step 16/23 : RUN msbuild .\src\Environment\identity\Mvp.Environment.Identity.csproj /p:Configuration=Release /restore /m /p:DeployOnBuild=true /p:PublishProfile=Local ---> Using cache ---> 4a5b5a23bcd6 Step 17/23 : WORKDIR .\src\Project\MvpSite\rendering\ ---> Using cache ---> dc1758ca6faa Step 18/23 : RUN dotnet publish -c Release -o /build/rendering ---> Using cache ---> 4ceeda0d0316 Step 19/23 : FROM ${BASE_IMAGE} ---> ad675c9cb2d5 Step 20/23 : WORKDIR /artifacts ---> Using cache ---> 1306d4d07af8 Step 21/23 : COPY --from=builder /build/docker/deploy/sitecore ./sitecore/ ---> Using cache ---> b66383587003 Step 22/23 : COPY --from=builder /build/docker/deploy/identity/Config ./identity/Config ---> Using cache ---> 22c39cd8c4ee Step 23/23 : COPY --from=builder /build/rendering ./rendering/ ---> Using cache ---> 68e686d14d67 Successfully built 68e686d14d67 Successfully tagged mvp-solution:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building cd Sending build context to Docker daemon 2.56kB Step 1/15 : ARG BASE_IMAGE Step 2/15 : ARG SOLUTION_IMAGE Step 3/15 : ARG TOOLS_RESOURCES_IMAGE Step 4/15 : ARG JSS_RESOURCES_IMAGE Step 5/15 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 6/15 : FROM ${TOOLS_RESOURCES_IMAGE} as tooling ---> 25d03b8c74d1 Step 7/15 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 8/15 : FROM ${BASE_IMAGE} ---> 3a1378b5e3d9 Step 9/15 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 37439d3b353d Step 10/15 : WORKDIR C:\inetpub\wwwroot ---> Using cache ---> 32868188e6ae Step 11/15 : COPY --from=tooling C:\tools C:\tools ---> Using cache ---> baafb78b3276 Step 12/15 : COPY --from=jss_resources C:\module\cd\content C:\inetpub\wwwroot ---> Using cache ---> c832a80d2380 Step 13/15 : COPY --from=jss_resources C:\module\tools C:\module\tools ---> Using cache ---> 1c6c181f8df8 Step 14/15 : RUN C:\module\tools\Initialize-Content.ps1 -TargetPath C:\inetpub\wwwroot; Remove-Item -Path C:\module -Recurse -Force; ---> Using cache ---> 22b9b4327922 Step 15/15 : COPY --from=solution /artifacts/sitecore/ ./ ---> Using cache ---> 607b7bf56982 Successfully built 607b7bf56982 Successfully tagged mvp-cd:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building id Sending build context to Docker daemon 2.048kB Step 1/8 : ARG BASE_IMAGE Step 2/8 : ARG SOLUTION_IMAGE Step 3/8 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 4/8 : FROM ${BASE_IMAGE} ---> da26fad74a8c Step 5/8 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 5eb42c09b3f2 Step 6/8 : WORKDIR C:\Identity ---> Using cache ---> 8970732729a6 Step 7/8 : COPY --from=solution /artifacts/identity/ ./ ---> Using cache ---> f99ee6df4cbc Step 8/8 : ENTRYPOINT ["dotnet", "Sitecore.IdentityServer.Host.dll"] ---> Using cache ---> af5d60d303f9 Successfully built af5d60d303f9 Successfully tagged mvp-id:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building cm Sending build context to Docker daemon 2.56kB Step 1/18 : ARG BASE_IMAGE Step 2/18 : ARG SOLUTION_IMAGE Step 3/18 : ARG TOOLS_RESOURCES_IMAGE Step 4/18 : ARG DEVEX_RESOURCES_IMAGE Step 5/18 : ARG JSS_RESOURCES_IMAGE Step 6/18 : FROM ${SOLUTION_IMAGE} as solution ---> 68e686d14d67 Step 7/18 : FROM ${TOOLS_RESOURCES_IMAGE} as tooling ---> 25d03b8c74d1 Step 8/18 : FROM ${DEVEX_RESOURCES_IMAGE} AS devex_resources ---> 96423725498a Step 9/18 : FROM ${JSS_RESOURCES_IMAGE} AS jss_resources ---> c8184866090a Step 10/18 : FROM ${BASE_IMAGE} ---> 4719259d16de Step 11/18 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] ---> Using cache ---> 1dc6457cd443 Step 12/18 : WORKDIR C:\inetpub\wwwroot ---> Using cache ---> 85026e6b9b09 Step 13/18 : COPY --from=tooling C:\tools C:\tools ---> Using cache ---> 1e9e6ce84058 Step 14/18 : COPY --from=devex_resources C:\module\cm\content C:\inetpub\wwwroot ---> Using cache ---> 0bc72ef6b1e8 Step 15/18 : COPY --from=jss_resources C:\module\cm\content C:\inetpub\wwwroot ---> Using cache ---> f6621ec07eac Step 16/18 : COPY --from=jss_resources C:\module\tools C:\module\tools ---> Using cache ---> 283c62ff0712 Step 17/18 : RUN C:\module\tools\Initialize-Content.ps1 -TargetPath C:\inetpub\wwwroot; Remove-Item -Path C:\module -Recurse -Force; ---> Using cache ---> 0ffbf3881465 Step 18/18 : COPY --from=solution /artifacts/sitecore/ ./ ---> Using cache ---> 2de4d9067657 Successfully built 2de4d9067657 Successfully tagged mvp-cm:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them Building mvp-rendering Sending build context to Docker daemon 2.56kB Step 1/6 : ARG DEBUG_BASE_IMAGE Step 2/6 : ARG RELEASE_BASE_IMAGE Step 3/6 : ARG SOLUTION_IMAGE Step 4/6 : FROM ${DEBUG_BASE_IMAGE} as debug ---> bfc92bae8713 Step 5/6 : WORKDIR /solution/src ---> Using cache ---> 4b977209be5c Step 6/6 : ENTRYPOINT ["dotnet", "watch", "-v", "--project", ".\Project\MvpSite\rendering", "run", "--no-launch-profile"] ---> Using cache ---> 88f3435497e1 Successfully built 88f3435497e1 Successfully tagged mvp-rendering:10.1.0-ltsc2019
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Docker Compose is now in the Docker CLI, try docker compose up
mvp-site-master_redis_1 is up-to-date mvp-site-master_mssql_1 is up-to-date mvp-site-master_solr_1 is up-to-date Starting mvp-site-master_solr-init_1 ... Starting mvp-site-master_solr-init_1 ... done mvp-site-master_cd_1 is up-to-date mvp-site-master_cm_1 is up-to-date mvp-rendering is up-to-date Starting mvp-site-master_traefik_1 ... error
ERROR: for mvp-site-master_traefik_1 Cannot start service traefik: failed to create endpoint mvp-site-master_traefik_1 on network nat: failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)
ERROR: for traefik Cannot start service traefik: failed to create endpoint mvp-site-master_traefik_1 on network nat: failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)
ERROR: Encountered errors while bringing up the project.
Waiting for CM to become available...
Invoke-RestMethod: C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master\up.ps1:26:19
Line |
26 | … $status = Invoke-RestMethod "http://localhost:8079/api/http/routers …
| ~~~~~~~~~~~~~
| No connection could be made because the target machine actively refused it.
PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master> docker scan Docker Scan relies upon access to Snyk, a third party provider, do you consent to proceed using Snyk? (y/N) y Usage: docker scan [OPTIONS] IMAGE
A tool to scan your images
Options: --accept-license Accept using a third party scanning provider --dependency-tree Show dependency tree with scan results --exclude-base Exclude base image from vulnerability scanning (requires --file) -f, --file string Dockerfile associated with image, provides more detailed results --group-issues Aggregate duplicated vulnerabilities and group them to a single one (requires --json) --json Output results in JSON format --login Authenticate to the scan provider using an optional token (with --token), or web base token if empty --reject-license Reject using a third party scanning provider --severity string Only report vulnerabilities of provided level or higher (low|medium|high) --token string Authentication token to login to the third party scanning provider --version Display version of the scan plugin "docker scan" requires exactly 1 argument PS C:\ResourceFiles\3Chillies\DockerSitecore\MVP-Site-master>
From: Mark Cassidy @.> Sent: 04 June 2021 07:47 To: Sitecore/MVP-Site @.> Cc: stephenvselvaraj @.>; Author @.> Subject: Re: [Sitecore/MVP-Site] docker.errors.DockerException: Error while fetching server API version: (#24)
Someone on Sitecore Slack had this same issue the other day. Reportedly solved it like this:
The issue is the UpdateEnvCompose.ps1 script changed the encoding of .env. Solved the issue by creating a new file and pasting the values over (edited)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sitecore/MVP-Site/issues/24#issuecomment-854408568, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUISMWTXY32KB4FFZQFQJYDTRBZHBANCNFSM46BUDVJQ.
EMAIL DISCLAIMER: This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of 3chillies Limited unless otherwise stated. Registered office: 3chillies Limited, Unit 6, Beacontree Plaza, Gillette Way, Reading Berkshire RG2 0BS, United Kingdom.
This error here; failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)
is because you have local IIS and/or SQL server running on the machine. Possibly local SOLR as well. Stop those services.
Hi Mark,
Thanks,
Yes finally it is now installed after stopped the IIS, SQL, SOLR and restarted the pc. But preciously I didn’t notice which process cause the issue. I still in dilemma to see this containerisation and digest by myself since this is the very first time understanding physical implementation.
XP Setup question, We are planning to follow this method to setup developer machines.
I am nobody but I do really respect Mark and Rob for the support, Valuable people. Thanks
@.***D75920.9AAA3330]
@.***D75920.9AAA3330]
@.***D7591E.5C60AED0]
From: Mark Cassidy @.> Sent: 04 June 2021 08:17 To: Sitecore/MVP-Site @.> Cc: stephenvselvaraj @.>; Author @.> Subject: Re: [Sitecore/MVP-Site] docker.errors.DockerException: Error while fetching server API version: (#24)
This error here; failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20) is because you have local IIS and/or SQL server running on the machine. Possibly local SOLR as well. Stop those services.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sitecore/MVP-Site/issues/24#issuecomment-854426235, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUISMWVDFQONVQB337UUPIDTRB4XTANCNFSM46BUDVJQ.
EMAIL DISCLAIMER: This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of 3chillies Limited unless otherwise stated. Registered office: 3chillies Limited, Unit 6, Beacontree Plaza, Gillette Way, Reading Berkshire RG2 0BS, United Kingdom.
Hi Rob,
Thanks,
Yes finally it is now installed after stopped the IIS, SQL, SOLR and restarted the pc. But preciously I didn’t notice which process cause the issue. I still in dilemma to see this containerisation and digest by myself since this is the very first time understanding physical implementation.
XP Setup question, We are planning to follow this method to setup developer machines.
I am nobody but I do really respect Mark and Rob for the support, Valuable people. Thanks
@.***D75921.05385650]
@.***D75921.05385650]
@.D75921.05385650] From: Rob Earlam @.> Sent: 04 June 2021 06:38 To: Sitecore/MVP-Site @.> Cc: stephenvselvaraj @.>; Author @.***> Subject: Re: [Sitecore/MVP-Site] docker.errors.DockerException: Error while fetching server API version: (#24)
Those error's dont tell enough really, can you post the full console output?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sitecore/MVP-Site/issues/24#issuecomment-854373123, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUISMWT2UXB2PCYPCDKD3WTTRBRDXANCNFSM46BUDVJQ.
EMAIL DISCLAIMER: This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of 3chillies Limited unless otherwise stated. Registered office: 3chillies Limited, Unit 6, Beacontree Plaza, Gillette Way, Reading Berkshire RG2 0BS, United Kingdom.
Thanks for confirming this is solved, I'm going to close this issue now.
For your follow on questions I would recommend joining the Sitecore Communuty Slack, there is a docker
channel in there that would be a better location for those discussion type questions.
Description
docker.errors.DockerException: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.') [26416] Failed to execute script docker-compose
Expected behavior
I am creating a POC and expect to install sitcore MVP-Site in my local development machine.
Steps To Reproduce
Your Environment
Following are my machine details: .NET Framework version = 4.8.4084.0 Powershell version = 7.1.3 Windows 10 = Pro System Type =64-bit x64-based processor Net.SecurityProtocolType = SystemDefault Ssl3 Tls Tls11 Tls12 Tls13
Screenshots