Various threads at CFD-Online that don't have an answer yet for the Docker-based installations

Forgot to mention about these two:

http://www.cfd-online.com/Forums/openfoam-installation/177354-openfoam-plus-docker-running-paraview-parafoam.html - I only gave an answer asking for more details.
http://www.cfd-online.com/Forums/openfoam-installation/176649-openfoam-plus-v1606-flag-provided-but-not-defined-privileged.html

Reassigned to @Pawan

@Pawan I'm not familiar enough with what goes inside the installers that are being used on Windows, so I have not idea where the problem with --privileged might be coming from.

Either way, you have a few more people with the same problem on this thread: http://www.cfd-online.com/Forums/openfoam-installation/176649-openfoam-plus-v1606-flag-provided-but-not-defined-privileged.html - I moved their posts into that thread a few minutes ago.

@wyldckat I am unable to reproduce issue in my machine.. Anyhow --privileged , is not necessary in windows . Sometimes, during installation, it does not find docker file and then download the latest version of this file from docker repository which in turn can make whole thing unstable. I will check with user whether he is able to resolve the issue

Took me a while to think about what you wrote... If the installer for Windows already provides the container, then it should not need to go look for one online?

And the other detail that I only noticed just now is that the first post on that thread is point the 32-bit path:

C:\Program Files (x86)\ESI\OpenFOAM\1606>"C:\Program Files (x86)\ESI\OpenFOAM\1606\Windows\Scripts\of_start_container.exe"

This should not be much of a problem, since the executables are acting as scripts, therefore it doesn't matter much if they are 32-bit or 64-bit, but for consistency sake, it would be good that sometime in the future, that the installation is made on the 64-bit location C:\Program Files (assuming the Windows executables are also 64-bit) ;)

Here are a few more threads that I don't know the answer for... although I tried to at least give a push in the right direction for two of them:

Thanks Bruno. I will help them in resolving the issue .

Hi Pawan,

From the thread [OpenFOAM plus] Start error (Windows 10) "no such container of_plus_1612" - specifically post #2 is the following information for another FAQ that should be added at http://www.openfoam.com/download/install-binary-windows.php

actually I found a solution: after creating a new Win10 user with admin attribution and a name that lacks spacing and accent, the installation worked perfectly

The error message was:

Error response from daemon: No such container: of_plus_1612
Error: failed to start containers: of_plus_1612
Error response from daemon: No such container: of_plus_1612

I have the very vague idea of seeing a post of yours with a similar answer, but I was not able to find it at CFD-Online's forum.

Best regards, Bruno

Hi Bruno

Error message indicates that container has not been created . There could be two reason for it
i) Either user has not clicked on OF_Env_Create shortcut which need to be done after installation once only .
ii) Or , because of some issue , the creation of container failed. User should check what error message it get from step above In most of cases, it is because username has space in it and script fail to take care of it . So easiest solution change username so that it cannot contain any space in it .

Regards Pawan

Hi Pawan,

My apologies, but I haven't managed to come by the forum(s) in the last few weeks and today I won't be able to answer to everyone. This to say that the following list of threads on this topic are not yet answered/solved (all the way back to the 12th of May):

Best regards, Bruno

HI Bruno Thanks for pointing . I have answered them all . I will keep track on them

Thanks Pawan

Hi @Pawan,

I forgot to point it out to you last weekend, regarding this thread: https://www.cfd-online.com/Forums/openfoam-installation/192283-openfoam-v1706-windows-10-installation-problem.html

It's not Docker related, but it's Windows WSL+Ubuntu related... which is somewhat similar :)

But unfortunately I haven't had the time to try it out myself, so I don't even know what types of situations that might occur in this structure.

Best regards, Bruno

@Pawan: Here is another thread, this time on issues with Docker and launching ParaView with OpenFOAM-v1706: https://www.cfd-online.com/Forums/openfoam-installation/192942-openfoam-v1706-parafoam-failed-start.html

@Pawan: Here is another thread: https://www.cfd-online.com/Forums/openfoam-installation/197146-openfoam-v1706-openfoam-windows-not-running.html - the post was originally lost within some other unrelated thread.

@Pawan: Here is a very recent thread, this is for Windows 7: https://www.cfd-online.com/Forums/openfoam-installation/209965-openfoam-installation-v1806-w7-64bit-problem.html

@Pawan: Just to give you a quick heads up: In an attempt to improve community support at CFD-Online, we have merged the two installation forums (the second one was for unsupported systems) into a single forum. This was both because Windows and Mac OS X are currently supported, and because some new forum members were posting about Docker and WSL based instructions on the second forum instead of the main forum.

We have also added new prefixes and have already sorted a good chunk of threads that are referring to OpenFOAM from ESI-OpenCFD with the prefix [OpenFOAM.com], which you can access directly the list here in case you want to have a direct bookmark.

Forum members are now forced to choose which prefix their new thread refers to, so we are hoping that this will make it easier for you and your colleagues at ESI-OpenCFD to find the threads referring to your releases!

Thanks @wyldckat
quite helpful

closed

reopened

@Pawan: I'm not familiar enough with Docker and since this refers to OpenFOAM v1812, when you get a chance, please look into this thread: https://www.cfd-online.com/Forums/openfoam-installation/218252-installing-v1812-windows-10-a.html

@Pawan The old docker installer for OpenFOAM-v1606+ either has an outdated certificate or it's something else entirely: https://www.cfd-online.com/Forums/openfoam-installation/219066-openfoam-v1606-could-not-read-ca-certificate.html

Various threads at CFD-Online that don't have an answer yet for the Docker-based installations

Child items

Activity

Admin message

Various threads at CFD-Online that don't have an answer yet for the Docker-based installations

Child items

Linked items

Activity