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

MVP - Change build image process - Wazuh dashboard #1690

Open
4 tasks
vcerenu opened this issue Jan 15, 2025 · 0 comments
Open
4 tasks

MVP - Change build image process - Wazuh dashboard #1690

vcerenu opened this issue Jan 15, 2025 · 0 comments
Labels
level/subtask Task issue

Comments

@vcerenu
Copy link
Member

vcerenu commented Jan 15, 2025

Description

According to the main issue, it is necessary to modify the installation process of the Wazuh dashboard packages in the Docker image build.

Within the Dockerfile we have a script that currently configures the pre-release or production repository according to whether the version we are using is greater or not than the current release.

COPY config/check_repository.sh /
RUN chmod 775 /check_repository.sh && \
    source /check_repository.sh

This script currently performs checks to automatically choose which repository to use. This must be modified so that it selects which package to download for the installation, taking into account that it can obtain the production and pre-release packages and also the possibility of using development packages, which must be obtained from private buckets.

Other steps of this change is to be able to build both amd64 and arm64 images, so the Dockerfile must be adapted to use global variables when selecting the corresponding architecture package.

It is also required to use a Github Actions workflow to build and push images to the corresponding repository. Currently, there is a workflow located at .github/workflows/Procedure_push_docker_images.yml that creates the Docker images and pushes them to Docker Hub. A workflow must be generated for the image's own build and its subsequent push to Docker Hub or ECR, depending on whether it is a productive image or not.

Tasks

  • Modify installation method to use downloaded packages
  • Ensure you can use prod, pre-release and development packages during the build process
  • Ensure you can create amd64 and arm64 images
  • Ensure the build workflow can push images to Docker hub and ECR repositories.

DRI

Gonzalo Acuña

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

No branches or pull requests

1 participant