Replies: 3 comments 16 replies
-
First, I will address the number 1 which I believe no one will object to. |
Beta Was this translation helpful? Give feedback.
-
From @VRichardJP :
Considering these, I would propose to have an image without artifacts for development and CI purposes. And in the CI, we can download the required artifacts when necessary too. I think CI doesn't even need the artifacts to function. Related discussion: |
Beta Was this translation helpful? Give feedback.
-
Related: |
Beta Was this translation helpful? Give feedback.
-
Code of Conduct
Contents
As a result of introducing cache into the CI workflows of the
autoware
andautoware.universe
, the execution speed has increased several times. However, as a side effect, GitHub-Hosted Runner frequently fails to execute jobs due to theNo space left on device
issues for example: https://github.com/autowarefoundation/autoware/actions/runs/9981995778/job/27586843983#step:5:18544.Therefore, slimming down the container image sizes is the next urgent task.
Several countermeasures can be considered.
Refine.dockerignore
to minimize the amount of files being copied.Stop copyingsrc
and temporarily mountsrc
withRUN --mount=type=bind
. https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/reference.md?utm_source=pocket_reader#run---mounttypebindpackage.xml
which is already mentioned by @oguzkaganozt More Strict Dependency Control for ROS Nodes #4599.Stop inserting artifact files into the image but there is also opposing opinion on this feat(docker): fix CUDA compile on devel image and improve run.sh #4849 (comment).I'm also definitely looking for ideas from you all.
Beta Was this translation helpful? Give feedback.
All reactions