Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add build scripts for building Nvidia and Neuron AMIs based on AL2023 #1924
Add build scripts for building Nvidia and Neuron AMIs based on AL2023 #1924
Changes from 4 commits
d93aaf1
286f29e
a202745
5c8ff3e
f6d066b
e856195
ef0d9a6
351d45c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SystemdCgroup = true
, etc. so they don't get lost during merge, you should be able to just swap the order of the args you're passing toutil.Merge
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.nvidia]
and[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.nvidia.options]
are not present inconfig.template.toml
, so if we want them to present in the resulting config, we'll have pass everything we need as is (SystemdCgroup, BinaryName, etc).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see what you mean. That's really not ideal, we don't want to have to keep this blob in sync with what the rest of the config flow does to these nested structs. Does the nvidia-ctk clone your existing runtime config and just change the name? How does this work there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvidia-ctk
uses/etc/containerd/config.toml
as base and does an in-place change (adding whatever it needs to the base). This is why initially I was writing the config file first, calling nvidia-ctk, passing the resulting config back. Let me see what will happen if we call it on empty file and merge with our template.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering about how
nvidia-ctk
handles options likeSystemdCgroup
,base_runtime_spec
, etc. It must be copying our existingrunc
runtime config and just plugging innvidia
andBinaryName
.Could you just update our existing containerd config template such that you can swap in
nvidia
? https://github.com/awslabs/amazon-eks-ami/blob/main/nodeadm/internal/containerd/config.template.tomlThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I addressed that, check the latest code.