-
Notifications
You must be signed in to change notification settings - Fork 522
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
Does conda install of deepmd support Platform: linux-aarch64? #3932
Comments
thanks. This is required by newest hpc in CSCS (https://www.cscs.ch/computers/decommissioned/toedi). Looking forward to the update. |
Hi, aarch64 is also required by the docker image. Does the docker iamge also suffer from the problem of upstream (tensorflow)? I only found x86 docker image for tensorflow in dockerhub (https://hub.docker.com/r/tensorflow/tensorflow/tags?page=2&page_size=&ordering=&name=) |
Currently, we build docker images just using the offline installer, maintained at https://github.com/deepmd-kit-recipes/docker-images. |
Hello, I checked the dockerfile. The offline installer only has linux x86_64.sh. How do you build the offline installer? Do we need to build an arm64 offline installer? |
The offline package is built at https://github.com/deepmd-kit-recipes/installer, which is a collection of conda packages. |
Thank you. It seems everything goes back to the |
memo: the containerfile for linux-aarch64 has been made by the cscs engineer, and the software performs well. |
Hello, I also want to use deepmd in linux-aarch64 and I want to know how to install it in linux-aarch64. I will also use dpmd in toedi. Thanks! |
Summary
no
DeePMD-kit Version
x
Backend and its version
x
Python Version, CUDA Version, GCC Version, LAMMPS Version, etc
No response
Details
I tried to install deepmd-kit using conda
conda create -n deepmd deepmd-kit lammps horovod -c conda-forge
And the message is
I found there is only
linux-64
not linux-aarch64. I am not sure if the error is caused by the platform. if so, could we add support onlinux-aarch64
The text was updated successfully, but these errors were encountered: