I'm trying to test out docker containers running with a domain credential and I'm following these instructions from Microsoft Docs. I have created the Group MSA, which I'm pretty sure I've done correctly as I can run other services on my local computer using it.
I'm testing on a Windows 10 PC, running hyper-v docker containers.
I have built an image called sqltest. When I run the following, the container does evey as expected:
docker run -it sqltest
I tried creating active directory credentials using this command:
New-CredentialSpec -Name developerpcsql -AccountName developerpcsql
Calling Get-CredentialSpec confirms that the json file is created as expected, and it looks right when I open the file.
To run the container, I'm using:
docker run -it --security-opt "credentialspec=file://developerpcsql.json" sqltest
When I do that, it takes about 30 seconds and then I get the following error:
Error response from daemon: container d97082fab98c0205c0072b0a8b79fb7835c8e90828498428b976e378762cc412 encountered an error during Start: failure in a Windows system call: The operation timed out because a response was not received from the Virtual Machine hosting the Container. (0xc0370109).
To confirm it's not my container I've also tried using the standard microsoft/servercore container and get the same error.
Any ideas on what I'm missing?
It looks like it does not work for Windows 10.
Here you can find discussion on the topic
Virtualization-Documentation git repo
It does work as expected for Windows Server 2016 Hosted container.
Related
I had ChirpStack Docker-Compose container in my local Windows 10 PC. It was configured and running fine.
I did stupid thing. I was trying to make this system run on Azure by entering commands:
docker login azure
docker context create aci myacicontext
and some more ..
Finally I failed with Azure and now I would like my local docker run again by entering old good command that worked fine before Azure:
docker-compose up
Got error:
The platform targeted with the current context is not supported.
Make sure the context in use targets a Docker Engine.
I suppose this error is because I was loged in Azure and I executed command:
docker logout
But this not helped. How get my docker composer run on my Windows machine again?
I faced same issue and way to solve was to change context back to default
docker context use default
I'm new to using Docker (never used it before) and I'm running into these errors:
I installed the Docker for Windows and following the steps on this
tutorial, but Docker Desktop doesn't load up for me at all.
I tried to run the docker pull hello-world command but I'm getting the error: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
How do I fix this? Thanks
I have a Virtualbox 6.1.4 with Toolbox 19.03.1 installed on Windows 10 with an user with administrator access.
I created a machine called xpto, then I run the eval $(docker-machine env xpto) to turn it active.
I have a docker compose file with two services (postgres and my application), when I try to run the docker-compose command I got the error below:
ERROR: Couldn’t connect to Docker daemon - you might need to run `docker-machine start default
I percept that the first service (postgres) start ok, but when try to run the second command happens the error above.
I did it in other machines and runs well, only in one machine it is happening.
What can be?
I am trying to run a Docker image inside a Service Fabric cluster.
This image runs fine on my local machine. However, when I deploy it to either my local cluster or a cluster on Azure Service Fabric, it starts to crash.
I tried running the docker ps command on the machine. It shows a container image running, but after 5s when I run the command again, it shows an empty list.
My application is built using ASP.NET Core 2.0.7 and my container image is microsoft/aspnetcore:2.0.7-nanoserver-1709
I am using the below OS for my cluster:
Offer: WindowsServerSemiAnnual SKU:
Datacenter-Core-1709-with-Containers-smalldisk
I see the below error:
Error event: SourceId='System.Hosting',
Property='CodePackageActivation:Code:EntryPoint'. There was an error
during CodePackage activation.System.Fabric.FabricException
(-2147017731) Failed to start Container.
ContainerName=sf-2-4e0c854d-d2d9-458a-82c5-78da874dc520_6fd774de-4796-4563-ab3f-c3bbb4d49e0c,
ApplicationId=ServiceFabricApplicationType_App2,
ApplicationName=fabric:/ServiceFabricApplication. DockerRequest
returned StatusCode=InternalServerError with
ResponseBody={"message":"container
fb204978704c52917704f1f6985ec9a73c9e76596e7258ff0ffce93c9c5109e0
encountered an error during CreateContainer: failure in a Windows
system call
It's very likely that you're running into this because of a mismatch between the version of Windows inside the image vs the version on the host.
Check out the compatibility list here.
(It specifically mentions your error message.)
To resolve this, you could:
Rebuild the container based on the version of microsoft/nanoserver or microsoft/windowsservercore
If the host is newer, use docker run
--isolation=hyperv ... Run on a different host with the same Windows version
The goal is to run docker containers on my nanoPI in the same manner as on a ubuntu server machine.
I have recently run into the following error when attempting docker run -it kylemanna/openvpn:
standard_init_linux.go:185: exec user process caused "exec format error"
I also get the same error when executing docker-compose using the container approach
Since I get the problem whether I use docker compose or not, I am starting to think that the error might be my usage of docker on the nanoPI. It may not be supported in the same way.
However, I can execute other containers/images just fine, hello-world, ubuntu, etc.
How do I go about determining the cause of this error? Where is the source code for standard_init_linux.go:185? And, what am I doing incorrectly?
Through trial and error, I discovered that if I rebuilt the openvpn image directly from the github repository on the machine with which the container would be run using (docker build <url>), then this error was resolved for the openvpn container but not (yet) for docker-compose. I imagine rebuilding the docker-compose container will fix the issue with that one too.
This is most likely due to a binary not having been compiled for the machine type that I was using.
Source/Inspiration: https://github.com/moby/moby/issues/23865