Docker Images (Nightlies) Is Not Updated For A Month

[CihatAltiparmak]

Hello, Mr @SteveMacenski,

I am one of the users who utilizes your nightly docker images. As I predict, due to the billings of github packages, it's not allowed you to store soo many images 🙄 . (https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-packages/about-billing-for-github-packages) . Thereby, I have a suggestion here. What about to delete the outdated images(shortly release images) using these jobs in github workflow as I do in my project? If you wish, I can try to test it in three days and then submit a PR, or free at will, you can do it directly by using my codes or not. Will be looking forward to your ideas.

[SteveMacenski]

What about to delete the outdated images(shortly release images) using these jobs in github workflow as I do in my project?

Please open a PR, I'd love that :-) I'd want any enumerated release (ex 1.3.1) for ROS 2 distributions to never be deleted, but the nightlies which are not releases could be deleted after 30 days.

My understanding of this issue though is that only the Nightly for Rolling is failing by looking at the Actions. Until recently it was failing trying to install dependencies: https://github.com/ros-navigation/nav2_docker/actions/runs/14635691886/job/41066208482. Perhaps your remark is the issue? But I thought it was something to do with behavior tree cpp binaries being pulled.

Then, its failing most recently due to a warning escalated into a error https://github.com/ros-navigation/nav2_docker/actions/runs/14659070125/job/41139323217. So it seems that previous error is gone (which aligns with my BT.CPP assumption). Interestingly, we fixed that about 2 weeks ago ros-navigation/navigation2#5114. It hasn't run since but it looks like that's because GitHub disables jobs in repos that haven't been touchediin 60 days.

I just poked the repo so that we can rebuild again -- see build: https://github.com/ros-navigation/nav2_docker/actions/runs/14659070125. That'll tell us where we're at today

PS: If you think your controller is ready for prime-time, happy to add it to the Nav2 plugins index!

[SteveMacenski]

@CihatAltiparmak it seems to be working again now!

I would still love the autodeleting thing just to not waste resources if you had a few minutes to contribute it :-)

[CihatAltiparmak]

Hi @SteveMacenski , unfortunately, I have no knowledge enough to contribute in a few minutes. I need to go dive into it. So, I thought that I take a look at it tomorrow. But maybe this job of moveit works out as well. But now, I am looking into it for your favor. (cant guarantee that I can open PR in no time)

[CihatAltiparmak]

Please open a PR, I'd love that :-) I'd want any enumerated release (ex 1.3.1) for ROS 2 distributions to never be deleted, but the nightlies which are not releases could be deleted after 30 days.

It doesnt sound sensible to me. But this can decrese the image number though. I will do what you say

My understanding of this issue though is that only the Nightly for Rolling is failing by looking at the Actions. Until recently it was failing trying to install dependencies: https://github.com/ros-navigation/nav2_docker/actions/runs/14635691886/job/41066208482. Perhaps your remark is the issue? But I thought it was something to do with behavior tree cpp binaries being pulled.

Ithink it is just because package name released by BehavaiorTree (u already know that) is changed. Maybe retriggering can fix it. Anyway, I will remark this if any.

PS: If you think your controller is ready for prime-time, happy to add it to the Nav2 plugins index!

Heartfeltly thank you for your interest. I have limited opportunity now and I tested my algorithms only on sim. But I may get some chance to test on the real robots of the company I worked. When it achieves its peak, I will communicate on slack platform.