-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Enable multi-stage builds for Autoware #2447
Comments
@LalithVipulananthan
Replacing the build.sh file would be the first step. |
@kasperornmeck cc @LalithVipulananthan The actual images hosted on https://github.com/autowarefoundation/autoware/pkgs/container/autoware-universe are created by these workflows and actions.
Regarding this part, could you first start with creating it as another script like |
@kenji-miyake |
@kenji-miyake |
@kasperornmeck No, they are not so different. The differences are just some settings. |
For the Perception PoC, to build all dependent components for perception, use the following command: |
@BonoloAWF - I suggest we close this issue as it won't go anywhere and the issues this issue tries to solve is addressed in the DevOps Dojos. |
Checklist
Description
Enable multi-stage builds for Autoware (eg: using Docker Compose or another similar tool).
Purpose
Lay the ground work, with the right tool, to enable building Autoware.Universe as a microservices architecture.
Possible approaches
From https://docs.docker.com/compose/:
Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration.
Definition of done
build-compose.sh
that uses Docker Compose to build an Autoware container as a multi-stage build (the current local build script is /autowarefoundation/autoware/docker/build.sh)build-compose.sh
file and request a review from @kenji-miyakebuild.sh
script for local buildsThe text was updated successfully, but these errors were encountered: