I get the following error when trying the docker-compose up command on a fresh install, I'm installing on a external HDD, not on C:\.
I suspect it has to do with your docker daemon service thinking it's installed on C:.
Give this a try:
Source
Related
my environment :
MacOS M1 chip
VSCode version 1.66.2 arm64
local installed docker version : 20.10.22
I have situations that docker is not working in VSCode.
I already installed docker in local. But when I'm trying to connect docker in VSCode, repeatedly asking install docker extensions. (but I do have docker already ). and if I do reinstall with following the VSCode, the docker version was broken (changed to intel chip docker).
Does anybody know what's wrong?
Docker Extensions for VS Code have nothing to do with the Docker engine itself. They are like an additional layer of tools and commands over the installed Docker. E.g. they provide IntelliSense for editing Docker-related files, you can run Docker commands from F1 drop-down, etc. But you should be able to do all the required tasks even without Docker Extensions, e.g. from the Terminal in VS Code, but for this the path to Docker CLI (command line interface) should be added to PATH environment variable.
If you are getting failed to connect error then maybe Docker engine is not running. Please refer to https://docs.docker.com/desktop/install/mac-install/ and https://docs.docker.com/desktop/troubleshoot/overview/ about how to check if the engine is running and how to troubleshoot the issues.
If that doesn't help, please provide some specific error and steps, which led to it, then we'll try to find out.
I installed Docker desktop latest version (Docker Engine - v20.10.22).
pointed it to search containers in Windows.
run the command docker --help (it is working okay)
Now when I am trying to run any command I am getting this error.
docker Error response from daemon: open
\.\pipe\docker_engine_windows: The system cannot find the file
specified.
did by any chance someone gets this error and got it resolved ?
I am relatively new for the docker technology.
Yesterday I setup docker on windows 10 machine and ran few dockers.
Today I first used command "docker system prune" so that I can run all of it once again without any conflicts.
But now I am firing below command:
docker run --name DockerName -v /c/collections:/etc/newman -t
postman/newman:ubuntu run
"MyAPITestCollection.postman_collection.json"
--environment="MyAPITestEnvironment.postman_environment.json" --reporters="json,cli" --reporter-json-export="reports/MyAPITestReport.json"
And getting below error:
error: ENOENT: no such file or directory, open 'MyAPITestEnvironment.postman_environment.json'
I haven't made any changes to the directories or anything else.
I checked the docker desktop setup option and found that the drive on which the file is located is still showing as the shared drive.
I tried by restarting the docker desktop several times and once by rebooting the machine as well but still found same error.
Kindly requesting to help me figure out the root cause of this issue and the solution as well.
My docker network had once again become public so firewall might be preventing the file access.
I changed it to private by using below command and it ran successfully:
Set-NetConnectionProfile -interfacealias "vEthernet (DockerNAT)" -NetworkCategory Private
I'm trying to use the OpenFOAM docker image. I installed everything correctly and when I try to run OpenFOAM_Start I get the error:
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Error response from daemon: No such container: of_1712
Error: failed to start containers: of_1712
Error: No such container: of_1712
Stopping "default"...
Machine "default" was stopped.
Then I ran docker-machine env command and I got the error:
Error checking TLS connection: Host is not running
I would appreciate if you could help me know what is the problem and how I can solve it.
P.S. Hopefully this is not off-topic. Please let me know if I should ask this question in a different stackexchange.
I found the solution but I'm still not sure what the error above mean. As indicated in the OpenFOAM installation guide, right after installation of the docker image you should run the:
"OF_Create_Env"
shortcut on the Desktop. A shell will open and close automatically,
completing setup of the user working environment. This step is mandatory
only on the first occasion of OpenFOAM for Windows installation.
Then you can run OpenFOAM_Start again and it just works.
I've tried running the official docker container on OSX10.11.
When I download and run on Kitematic, it gives me an error: Error: No config file found.
I've run the standard ubuntu container and it has worked correctly.
Any help would be appreciated.
I'm afraid so, we're currently looking into it as part of https://github.com/deepstreamIO/docker/issues/2