[instanton]

Hi, I'm trying to install v2312 in the latest continuumio/miniconda3 docker image, which is based on Debian 12 (bookworm). I've attached my dockerfile as a .txt (I'm building with the .dockerfile suffic, of course).

I am getting the classic error, E: Unable to locate package openfoam2312-default, despite bookworm being present in the repo. Not sure what could be causing this. I would love to start from the miniconda docker image, so any advice would be appreciated.

[olesen]

Originally Posted by instanton

Hi, I'm trying to install v2312 in the latest continuumio/miniconda3 docker image, which is based on Debian 12 (bookworm). I've attached my dockerfile as a .txt (I'm building with the .dockerfile suffic, of course).

I am getting the classic error, E: Unable to locate package openfoam2312-default, despite bookworm being present in the repo. Not sure what could be causing this. I would love to start from the miniconda docker image, so any advice would be appreciated.

Not sure where things are going wrong for you. The misc 'sudo' in your docker file look a bit odd. I just tried a manual install within a bookworm image with "apt-get install -y openfoam2312-default" and it installing the tutorials as I write.



It could be worth checking if modified versions of the regular docker files work for you, and go from there:
https://develop.openfoam.com/packagi...b/main/docker/


I think that those are a nice way to go since they do all of the fixes, setup files within the container and provide the nss-wrapper, which lets you easily map users into the container.

[instanton]

Originally Posted by olesen

Not sure where things are going wrong for you. The misc 'sudo' in your docker file look a bit odd. I just tried a manual install within a bookworm image with "apt-get install -y openfoam2312-default" and it installing the tutorials as I write.



It could be worth checking if modified versions of the regular docker files work for you, and go from there:
https://develop.openfoam.com/packagi...b/main/docker/


I think that those are a nice way to go since they do all of the fixes, setup files within the container and provide the nss-wrapper, which lets you easily map users into the container.

Hi Mark, thank you for responding and all the work that you do. By misc 'sudo', do you mean miscellaneous 'sudo' commands, or missing sudo commands?



I believe my issues with using the regular docker files involved the installation of python packages, which were solved by starting from the miniconda image... so I'm stuck trading off one problem for another, and the OpenFOAM issue seems to me maybe more manageable.



Could you try building the dockerfile I provided? It's a total mystery to me, but you might notice something that escapes a novice like myself.

[olesen]

Originally Posted by instanton

Hi Mark, thank you for responding and all the work that you do.

Definitely nice to hear warm words. It often feels like most of the work is for the "void" and nobody actually cares.

Originally Posted by instanton

By misc 'sudo', do you mean miscellaneous 'sudo' commands, or missing sudo commands?

When building docker images you are fundamentally always 'root', so I don't see why you would need to prefix anything with "sudo". Also, you have a RUN line with 'sudo -i' followed by other RUN lines, so the first one is probably irrelevant.
In general (once you get things debugged), you should reduce the number of separate lines since each one will correspond to an intermediate image layer, which increases your final image size.

Originally Posted by instanton

Could you try building the dockerfile I provided? It's a total mystery to me, but you might notice something that escapes a novice like myself.

I made a few changes (to remove some fluff) but didn't get it to work either. Instead I've mostly just avoided your problem and tackled it by adding the python stuff onto an OpenFOAM image - it does build, but I haven't tested it.
As for your swak4foam "work-in-progress". There are a number of things that swak does that can also now be done with the regular openfoam.com version. If (really useful) things are still missing, it would make the most sense to get these upstreamed into openfoam.com, but this of course requires effort/support/etc (this probably sounds like begging, but the resources have to come from somewhere).

[instanton]

Originally Posted by olesen

I made a few changes (to remove some fluff) but didn't get it to work either. Instead I've mostly just avoided your problem and tackled it by adding the python stuff onto an OpenFOAM image - it does build, but I haven't tested it.

Hi Mark- Thank you for your help! I was not able to successfully build the dockerfile you attached due to the following error

16.93 ERROR: Could not find a version that satisfies the requirement gmsh (from versions: none)
16.93 ERROR: No matching distribution found for gmsh

This is the error that I was having before when not using the miniconda image. Really, the other Python libraries don't have any issue--it seems to be one with gmsh.


You're right, I haven't found a need for swak4Foam, and I've managed to achieve a lot of what I would want from it by using codedMixed boundary conditions (I *really* wish the documentation for codedMixed and expressions was easier to track down and better maintained).


Again, thank you.

[olesen]

Actually it seems that I tested on ubuntu not debian, maybe that's the difference?

[instanton]

Originally Posted by olesen

Actually it seems that I tested on ubuntu not debian, maybe that's the difference?

Yes, I imagine it is. Starting from an ubuntu image, I have no issue with installing Openfoam. But really, I don't see any reason *why* the Debian image should be causing issues: it just seems to not be able to find the right files for the Debian build, based on the error I'm receiving.


I hope this is something that can be addressed on the OpenFOAM end of things: is there any reason why a Debian build should fail while the ubuntu does not? Some inconsistency in the file structure? Certainly some Debian users have had success with OpenFOAM builds, no?


Thanks, Mark.