Dockerized Gitlab CI runner for Python testing. Contribute to cardoe/docker-gitlab-ci-runner-python development by creating an account on GitHub. Oct 28, 2020 How to improve docker build time by leveraging different caching strategies while using Docker in Docker. Illustrated using GitLab CI and Kubernetes. Or compile the dependencies into a Python.

Gitlab Ci Python Docker Online

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:

• What version are you on? Are you using self-managed or GitLab.com?

  • GitLab (Hint: /help): Yes, on Gitlab.com
  • Runner (Hint: /admin/runners): Shared runners for this project is enabled

• Add 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

• What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
  • Attempted changing image to python:3.9, rather than the current value.

Gitlab Ci Build Docker Image

Thanks for taking the time to be thorough in your request, it really helps!