Why is DOCKER_BUILDKIT=0 explicitly set?

dusty-nv / jetson-containers

Machine Learning Containers for NVIDIA Jetson and JetPack-L4T

MIT License

2.09k stars 435 forks source link

Why is DOCKER_BUILDKIT=0 explicitly set? #352

Open ahi-bplus opened 8 months ago

ahi-bplus commented 8 months ago

I would like to build my own packages and need BuildKit. Why is BuildKit explicitly disabled?

https://github.com/dusty-nv/jetson-containers/blob/6f0d65ed3884430d099bf3ffb7777318a6277f9e/jetson_containers/container.py#L105

Thanks for your help.

champred commented 1 month ago

Apparently BuildKit doesn't allow access to the NVIDIA container runtime which is needed for CUDA libraries. I don't believe there's a workaround, but if there is one it would be nice to know.

dusty-nv commented 1 month ago

Yes, unlike vanilla docker build it does not honor the default docker runtime during container builds. If you find a workaround or that it is fixed, let me know too!