Skip to content

Conversation

lxjanoo
Copy link

@lxjanoo lxjanoo commented Apr 20, 2022

There will be 2 images created for fluent. Images created

  • fluent-solver + nexus ( ghcr.io/pyansys/pyfluent-solver )
  • fluent-solver + nexus + cad ( ghcr.io/pyansys/pyfluent )

dockerfiles

  • Dockerfile ( ghcr.io/pyansys/pyfluent-solver )
  • Dockerfile.meshing ( ghcr.io/pyansys/pyfluent builds on ghcr.io/pyansys/pyfluent-solver )

The tgz files to create the images are defined in a txt file

ceiList.txt list of nexus files
fluentList.txt list for fluent files for standalone fluent
cadList.txt List of meshing files needed by fluent

Steps to create images:

  • Install latest certified WB for fluent
  • create the tgz files
  • create the docker images

REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/pyansys/pyfluent latest e3e02d29b00a 2 hours ago 15.3GB
ghcr.io/pyansys/pyfluent-solver latest dab4309453de 2 hours ago 8.52GB

Ran basic test to import cad and run a solver journal file.

COPY cad.tgz /ansys_inc/
RUN tar -xzf /ansys_inc/cad.tgz --directory /ansys_inc/ && rm -f /ansys_inc/cad.tgz

FROM ghcr.io/pyansys/pyfluent-solver:latest AS fluent
Copy link
Collaborator

@dnwillia-work dnwillia-work Apr 20, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, so is this taking the first image and incorporating here? If so, I think the ci config will need updating to pull this image.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Using the solver image to add to it the cad piece.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think I need to update this. The docker pull command will be installing ghcr.io/pyansys/pyfluent:latest which will be the fluent + nexus + cad ( full fluent )

docker should pull ghcr.io/pyansys/pyfluent-solver:latest which will be just fluent + nexus when installing the full fluent

Unless we want to have a Makefile for fluent-solver & fluent-solver + cad ( full fluent )

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, good and we can leave the makefile as it is.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a thought of creating docker images of the 3 tgz files ( cad, cei, fluent ) in github

Then have dockerfiles to create the images from the tgz images. Based on the 3 tgz files, we could create 3 images if we need to.

base fluent solver: fluent tgz image
base fluent solver + parametric: fluent + cei tgz images
base fluent solver + parametric + meshing: fluent + cei + cad tgz images

Wondering if there is any interest in this approach. I will not merge this PR if there is interest in this.

Copy link
Collaborator

@dnwillia-work dnwillia-work Apr 21, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be ok but splitting out CEI probably only makes sense if we also deactivate the dependent part of the API. So, we would need to do both bits of work. I think you could leave it aside for now.

@dnwillia-work dnwillia-work merged commit 7088c9c into main Apr 21, 2022
@dnwillia-work dnwillia-work deleted the fix/multipledockerimages branch April 21, 2022 22:45
@dnwillia-work
Copy link
Collaborator

@lxjanoo Sean is away this week so I force merged the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants