You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running deploy/scripts/build.py, the builds are not automatically loaded in Docker as before.
To Reproduce
Steps to reproduce the behavior:
Delete all local Docker images, containers, builds for The Combine
Start a Python virtual environment (venv)
Run python deploy/scripts/setup_cluster.py --type development
Run python deploy/scripts/build.py
Run docker images and see that the desired images aren't present
Run kubectl -n thecombine get deployments and see 0/1 in the READY column (should be 1/1)
Run kubectl -n thecombine get pods to get failed pod names (e.g. backend-9d66df89b-m25pq)
Run (e.g.) kubectl -n thecombine logs backend-9d66df89b-m25pq to see that the image failed to pull
Run python deploy/scripts/build.py --debug and you may notice warning like
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
It seems some Docker or buildx update no longer loads our builds by default and we need to add --load to the docker buildx build [...] commands.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running
deploy/scripts/build.py
, the builds are not automatically loaded in Docker as before.To Reproduce
Steps to reproduce the behavior:
(venv)
python deploy/scripts/setup_cluster.py --type development
python deploy/scripts/build.py
docker images
and see that the desired images aren't presentkubectl -n thecombine get deployments
and see0/1
in the READY column (should be1/1
)kubectl -n thecombine get pods
to get failed pod names (e.g.backend-9d66df89b-m25pq
)kubectl -n thecombine logs backend-9d66df89b-m25pq
to see that the image failed to pullpython deploy/scripts/build.py --debug
and you may notice warning likeIt seems some Docker or buildx update no longer loads our builds by default and we need to add
--load
to thedocker buildx build [...]
commands.The text was updated successfully, but these errors were encountered: