-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[BUG] Docker Build Fails at pip install megatron-core==0.4.0
#650
Comments
Related issue: NVIDIA/NeMo-Framework-Launcher#184 |
I believe it could be fixed by:
|
Not that this is a valid solution, however I was facing the same issue while installing nemo_toolkit[all] and I reverted the version of the package to the previous one nemo-toolkit==1.21.0 released in 2023 as opposed to the current one which released in Jan 2024. |
Encountered the same issue as the OP -- indeed it seems this repo is missing a https://setuptools.pypa.io/en/latest/userguide/miscellaneous.html |
Thanks @JanuszL you’re right, I missed that. |
Marking as stale. No activity in 60 days. |
Closing bug. Will track the issue on the new ticket. |
Describe the bug
There is an error in building the Docker image for a project dependent on Megatron-LM (https://github.com/NVIDIA/NeMo-Megatron-Launcher). The build process gets stuck during the package installation phase, specifically at
pip install megatron-core==0.4.0
.To Reproduce
Steps to reproduce the behavior:
pip install megatron-core==0.4.0
step.Expected behavior
The Docker build should proceed without errors and successfully install all required packages, including
megatron-core==0.4.0
.Stack trace/logs
Environment:
Proposed fix
Currently, I do not have a proposed fix. I am hoping the maintainers can provide insight or a fix for this issue.
Additional context
megatron_core
version 0.4.0. Notably, when usingmegatron_core
version 0.3.0, the build process completes successfully. This suggests that the problem may be isolated to changes introduced in version 0.4.0 ofmegatron_core
.The text was updated successfully, but these errors were encountered: