Describe your question in as much detail as possible:
In my AWS SAM build-and-package step, the docker container fails to pull an image of python3.9. This issue suddenly started happening, and was note occurring in previous builds. Not sure if it’s an issue w/ docker containers, or not?
What are you seeing, and how does that differ from what you expect to see?
I’m expecting the build to be successful, like below:
Consider including screenshots, error messages, and/or other helpful visuals
Below is what I’m currently seeing:
First thing after importing repository into gitlab we need to create.gitlab-ci.yml. Gitlab itself has a lot of useful information about CI configuration, for example this and this. Previously I used to do following steps to test/compile/deploy manually: npm run build - to build all js/css; build.sh - to build docker container. In the root of your project, create a.gitlab-ci.yml file, set the following code, and substitute the #S3NAME# with the Amazon S3 bucket name you made to save the package: image: python:3.8 stages: - deploy Dev: stage: deploy beforescript: - pip3 install awscli -upgrade - pip3 install aws-sam-cli -upgrade script: - sam build - sam package.
What version are you on? Are you using self-managed or GitLab.com?
/help
): Yes, on Gitlab.com/admin/runners
): Shared runners for this project is enabledAdd the CI configuration from .gitlab-ci.yml
and other configuration if relevant (e.g. docker-compose.yml)
https://gitlab.com/qzeng96/vibes/-/blob/main/.gitlab-ci.yml
image
to python:3.9, rather than the current value.Thanks for taking the time to be thorough in your request, it really helps!