Skip to content
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

l4t_version_compatible() wrongly flags JetPack6 R36 images as compatible on JetPack5 R35 hosts #353

Open
frostydonut opened this issue Dec 14, 2023 · 4 comments

Comments

@frostydonut
Copy link

if l4t_version.major >= 35:

">=35" should be "==35" ??

@dusty-nv
Copy link
Owner

Ahh thanks @frostydonut , you are correct! Just fixed this in 2b178c8

Note that if it pulled any r36.2.0 images to your system, you should remove them with docker rmi, because autotag will defer to your local images first (and for those it doesn't do version checks). Once you have r36.2.0 removed, it will check dockerhub again for r35 images if you pull the latest jetson-containers that includes the patch above.

@frostydonut
Copy link
Author

frostydonut commented Dec 14, 2023 via email

@adamwhats
Copy link

Hi @dusty-nv, what are the ramifications of running r36.x images on an r35.x host? I've just sat down to try and use the humble-ros-base-l4t-r36.2.0 on my Xavier NX. My thought (hope) was that I could run the majority of my ROS nodes in that newer humble container, and then put the few which use GPU in to a separate roxy/r35.x container

@dusty-nv
Copy link
Owner

@frostydonut no problem, happy to be of service!

@adamwhats the r36 images aren't compatible with r35, not for GPU at least. Otherwise, yea you can run whatever as long as it was built for aarch64. And if you aren't using GPU for some nodes, then you can just run the upstream OSRF ROS containers for those: https://github.com/osrf/docker_images my guess is you would prefer one with a 22.04 base since that has tier-1 support for Humble and their debian packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants