unable to run OpenFOAM docker image - docker

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.

Related

Using docker context to a mac

I had been trying to create a context to deploy a few containers from my main Mac to another another but I have been getting a weird error.
So, I have two Macs, one iMac (Late 2013) (here will be called Enterprise) and one Macbook Pro (Mid 2015) (here will be called Defiant). Defiant is my main computer and I want to deploy my container to Enterprise in order to not overload Defiant memory. I have been working with docker context to achieve that. Currently, I have Enterprise running Docker v20.10.16 and Defiant running v20.10.16.
I have created the context on Defiant and after I run the docker context use enterprise and when I run docker container ls I get the following error:
error during connect: Get "http://docker.example.com/v1.24/containers/json": command [ssh -l rafaelguerra -- Enterprise.local docker system dial-stdio] has exited with exit status 127, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=zsh:1: command not found: docker
Does anyone know how to make it work?
Thanks
UPDATE:
Weird thing I just found out, when logged into Enterprise and run echo $PATH returns /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin however when I run ssh rafaelguerra#enterprise.local 'echo $PATH' I got the following /usr/bin:/bin:/usr/sbin:/sbin
I don't have a clue for a reason for this.
I found the reason for the problem, all commands docker run are run within ssh not with a permanent ssh session. So, zsh does not load the correct PATH when the command is run within the ssh. Therefore, the only thing I need to do was setting the correct PATH inside of the ~/.zshenv file and everything is working now.

Docker commands and setup running successfully yesterday started giving error "ENOENT" today suddenly on windows 10

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

Docker for windows issue while installing and running

I have been trying to install Docker for windows in Windows 10 pro edition but I am getting always error in cmd or powershell when I type docker info I am getting result like this
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.26/info: open //./pipe/docker_engine: 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.
I have installed using InstallDocker.msi file but not able to fix this issue. I dont have any VM or Virtual Box running and I have make sure that Hyper-V and Virtualisation has been enabled in my PC. Please help me in this issue.
Thanks In Advance.
Did the installation end successfully with the Docker welcome window?
If not, probably something went wrong during the installation.
You can either reinstall it or try to follow answers in this issue:
https://github.com/docker/docker/issues/22338

deepstream.io docker run error on OSX

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

Running HHVM's "hh_server" tool inside Docker container fails

Running HHVM's hh_server tool in Docker fails with following error:
Fatal error: exception Not_found.
Same tool works fine in the host with same OS (Ubuntu 14.04) and HTTP server (nginx).
Any idea how this might occur?
I had the exact same problem on a Debian image. After talking to a guy at hhvm's IRC channel I got it working by setting the USER environment variable to a username. Apparently hh_server don't work if USER is empty

Resources