krutopush.blogg.se

1. #OPENFOAM WITH DOCKER FOR MAC INSTALL#
2. #OPENFOAM WITH DOCKER FOR MAC CODE#
3. #OPENFOAM WITH DOCKER FOR MAC WINDOWS#

I’ve made some changes to my container.How do I get my data into & out of the container?.Building your own OpenFOAM Docker image.What problem does Docker solve for CFD?.

What is Docker? Why is it useful for CFD? What is it good/not-so-good for? And, most importantly, how do you actually use it? That’s what I hope this updated version might achieve. But I think there’s still some confusion about using OpenFOAM with Docker. Since then, both OpenCFD & The OpenFOAM Foundation have started distributing Docker-ised versions of their respective releases, easing these issues.

#OPENFOAM WITH DOCKER FOR MAC CODE#

Hopefully this impementation doesn't mangle the existing code too much. In this, paraview from the docker distribution is used so that all the environment variables are set correctly. Regarding a better way of integrating docker like bluecfd and bashwsl - should those two stay? Or is it better to remove them and move everything to docker as we should be able to get it working on windows, linux and mac?

#OPENFOAM WITH DOCKER FOR MAC WINDOWS#

I left the windows implementation to one side for the moment - this can be tested and issues resolved hopefully without too much fuss (the use docker button won't be visible on windows unless some trivial hide code is removed). Morning all, I have got something working but I don't think it is a particularly good implementation at the moment so perhaps not ready for a pull request. As long as these directories persist, it doesn't really matter if the source disappears.

#OPENFOAM WITH DOCKER FOR MAC INSTALL#

When they are compiled, hisa and cfMesh will install in the $FOAM_USER_LIBBIN and $FOAM_USER_APPBIN directories where they will be found by OpenFOAM (these variables should be defined inside the OpenFOAM environment).

However some people might object to needing a large home directory. You wouldn't want to recompile hisa each time tmp directory was deleted.įor the sake of simplicity and cleanliness I guess ii) would be better. Iii) while cfmesh-cfdof could be installed outside the container, I'm guessing hisa needs to be accessable by openfoam (but I haven't checked this) So I don't think we could get away from needing 2nd (non-tmp) directory. Ii) simply state that the temporary directory needs to be in the openfoam install directory I) modify the standard script so we mount the separate tmp directory (a second -v), I haven't looked to see if I need to add the platform bin and lib paths but shouldn't be a problem if need to.Į) /tmp - Unfortunately the standard openfoam7-xxx scripts don't allow us to mount two directories at once. They can stay in the platform directory under openfoam (which will stay present betwen container image creations). So both will need to be unziped outside the container and compiled inside the container. Openfoam7-paraview56 doesn't come with unzip by default. This will be used to compile hisa and cfmesh-cfdof. I haven't investigated any stdout/stderr redirect problems at this point, but they should be solvable if there are any.ĭ) Retain the openfoam install directory even though we will not be using the same way (if running docker, some of the validity checking code needs to be modified). Subsequent commands can be easily run in the already running container. I think initially make the docker option only available under macos and linux as there is already a good working solution for windows (bluecfd).ī) have entry for the Docker image name / runscript (default openfoam/openfoam7-paraview56 / openfoam7-linux/-macos)Ĭ) first time a container is required we run it and keep it running until freecad closes down. I've had a look at things and thought I'd outline my approach - so that developers can provide input if they don't like my approach.Ī) in preferences add a 'Use docker' qcheckbox.