-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which Docker Images do we need? #25
Comments
Yes, may be those three are sufficient. |
I will include an experimental image (including: temmeta, pyprismatic, match-series, and pyxem). But shall it be based on pyiron/base or pyiron/pyiron? In the case of later, the user have full simulation capabilities and experimental post-processing. |
Ideally the experimental part would be based on |
Our DAMASK example is coupled with LAMMPS, so |
Can you add the two Docker images for experimental and DAMASK? |
Sure, I am now in a meeting. I will add them just after the meeting. |
@muh-hassani Can you tell me which of the pyiron Docker Images you are currently using? |
@jan-janssen I use |
@jan-janssen I also use |
@jan-janssen I have started a branch to address this issue. |
So I will remove the branch that I was working on. |
Sorry I did not realise you were working on the same issue. |
As already mentioned in #23 (comment) while I previously suggested to have more images I guess it should be fine to reduce the number of images:
pyiron/base
- which includes -pyiron_base
pyiron/lammps
- which is based onpyiron/base
and additionally includespyiron
,nglview
andlammps
.pyiron/pyiron
- which is based onpyiron/lammps
and additionally includessphinx
andgpaw
.In addition we should include Dockerfiles for all images used on the internal server, especially the TEM and DAMASK examples.
The text was updated successfully, but these errors were encountered: