Closed cesar2000ab closed 1 year ago
@cesar2000ab
Thank you for your issue report!
I have already reproduced it locally in similar conditions:
The steps to reproduce it were:
t2d git@git.vauxoo.com:absa/absa.git 12.0
~/.t2d/script/git_git.vauxoo.com_absa_absa.git/12.0/3_5/env_1_job_1/10-build.sh --no-cache
It is similar to your video
We have deployed new changes in the t2d tool and we are using the same image as DeployV to match the CI with the CD with fewer variants
The new way needs 2 things:
1) Extra parameter --deployv
2) Request access to quay.io
I mean, running the commands:
t2d --deployv git@git.vauxoo.com:absa/absa.git 12.0
~/.t2d/script/git_git.vauxoo.com_absa_absa.git/12.0/3_5/env_1_job_1/10-build.sh --no-cache
You will see the following output:
Generated scripts:
- ~/.t2d/script/git_git.vauxoo.com_absa_absa.git/12.0/3_5/env_1_job_1
================================================================================
Using --deployv option you will need to run the following extra step manually after to create the container or after running 20-run.sh script
docker exec -it --user=root CONTAINER find /home/odoo -maxdepth 1 -not -user odoo -exec chown -R odoo:odoo {} \;
TIP: Use the parameter "--docker-image=quay.io/vauxoo/PROJECT:TAG" get the PROJECT:TAG info in your "build_docker" pipeline similar to
"... INFO - deployv.deployv_addon_gitlab_tools.common.common.push_image - Pushing image ... to quay.io/vauxoo/PROJECT:TAG"
Sending build context to Docker daemon 3.601MB=================================Sending build context to Docker daemon 557.1kB
Step 1/20 : FROM quay.io/vauxoo/absa:absa-12.0-bc1d6c2
absa-12.0-bc1d6c2: Pulling from vauxoo/absa
8f12f7a5869b: Downloading [=======================================> ] 5.436GB/6.828GB
...
Notice the step 1/20 is using docker image called quay.io/vauxoo/absa:absa-12.0-bc1d6c2
instead of old vauxoo/odoo-80-image-shippable-auto
The quay image is built from your CI and it is the same one used in deployv staging instances in the CD
So, request your project manager access to be able to download images from quay.
You can double-confirm if you have access using the following command:
docker pull quay.io/vauxoo/absa:absa-12.0-bc1d6c2
Before you need to log in with
docker login quay.io
your user and password
Also, consider that the extra comments in the output of t2d command as:
docker exec -it --user=root CONTAINER find /home/odoo -maxdepth 1 -not -user odoo -exec chown -R odoo:odoo {} \;
So, after creating the container you will need to run this extra command (replace CONTAINER by the real name of your CONTAINER)
The final output will be:
Step 20/20 : WORKDIR $MAIN_REPO_FULL_PATH
---> Running in 429598cba4b4
Removing intermediate container 429598cba4b4
---> 72b3deb12617
[Warning] One or more build-args [GITHUB_TOKEN] were not consumed
Successfully built 72b3deb12617
Successfully tagged absa-absa:12_0_3_5_1
tks Moy, Is neccesary that all Dev from ABSA IT has access to this quay.io/vauxoo/absa:absa-12.0-bc1d6c2
I run. ~/.t2d/script/git_git.vauxoo.com_absa_absa.git/12.0/3_5/env_1_job_1/10-build.sh --no-cache
and show the:
Is neccesary that all Dev from ABSA IT has access to this quay.io/vauxoo/absa:absa-12.0-bc1d6c2
Yes, it is.
It is related to my comment:
So, request your project manager access to be able to download images from quay.
I mean, you need to contact your project manager or support team in Absa to request access to https://quay.io/ Absa project with all your dev users
Regards!
Version:
Video:
https://grupoabsa.zoom.us/rec/share/IJPnHunVbPvXcviGNQnYFUjtpzncc8Cdyax6wGXcgHcUPh-axkd0MmhwUCIzJbuw.16Z4HSqmJRmK87aO?startTime=1676735713000 Código de acceso: wYDdGh4@