This short clip explains one of the more visible changes in Warewulf v4.6.0: node containers are now called images. The original term signaled that you could build node images with container ecosystem tools such as Docker, Podman or Apptainer, which is far nicer than hand-assembling a directory. But it led many people to assume some form of nested virtualization or containerization was running inside the node image and hurting performance.
In 4.6.0 the object is renamed to image or node image across the code, documentation and command line help. Behavior is identical, and container remains as an alias for anyone whose muscle memory has not caught up.
Key takeaways
- Warewulf v4.6.0 renames node containers to images throughout the code, documentation and command line help.
- The container name was meant to highlight building node images with Docker, Podman or Apptainer, not runtime containerization.
- Many users wrongly assumed nested virtualization inside the node image would impact performance, prompting the rename.
- Nothing changes functionally, and container is still accepted as an alias for the image command.
Questions this video answers
Does Warewulf run compute nodes inside containers?
No. Warewulf lets you define a node image with container tools such as Docker, Podman or Apptainer, but the provisioned node runs that image directly with no nested containerization or virtualization. Because the word container caused that confusion, Warewulf v4.6.0 renames the object to image while keeping container as an alias.
This video is part of the Warewulf Pro playlist. Browse every CIQ video by product and topic.
Transcript
our use of the term container here has been a confusion to many people uh it was meant to kind of indicate and uh and support the idea of using container ecosystem tools for building these node images so you can use um frankly you can use Docker or podman or Apptainer or any of these to define a node image which ends up being a really good um a really good experience compared to the old way of kind of creating a directory and kind of hacking an image together manually but this name Led people to think that there was some kind of nested virtualization or containerization happening
inside of the Warewulf node image that might impact performance uh and it just ended up being a surprising um a surprising bit of nomenclature so over in Warewulf 460 land this has been renamed to image uh it behaves exactly the same uh we can see oh uh long oh I can't type and talk at the same time uh there we go um we can see information about the images in our cluster uh but just for people whose muscle memory has already switched them to container uh that that's still present as an alias but all of the documentation all of the kind ofline help whether it's
on the website or in the um in the command line tool here um will expect to use the term uh image or node image now instead of container again not really a big functional change but it was kind of a big deal to go through all of the code and change all of the places that it says container to be image and not break things
Built for scale. Chosen by the world’s best.
2.75M+
Rocky Linux instances
Being used world wide
90%
Of fortune 100 companies
Use CIQ supported technologies
250k
Avg. monthly downloads
Rocky Linux
9
Enterprise products
Spanning the kernel to the orchestrator
Have questions about your infrastructure?
Talk to a CIQ engineer about Rocky Linux, HPC, and AI infrastructure.