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.

Sign up for GitHub

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

Jump to bottom

python-3.8-stretch docker image does not exist in python_basic template with gitlab cicd. #647

Open
j-4 opened this issue Dec 22, 2022 · 0 comments · May be fixed by #648
Open

python-3.8-stretch docker image does not exist in python_basic template with gitlab cicd. #647

j-4 opened this issue Dec 22, 2022 · 0 comments · May be fixed by #648

Comments

@j-4
Copy link

j-4 commented Dec 22, 2022 •
edited

Expected Behavior

The following command sets up the python_basic template with a .gitlab-ci.yml

dbx init --template=python_basic \
    -p "cicd_tool=GitLab" \ 
    ....

I would expect that the Gitlab CI/CD runs.

Current Behavior

WARNING: Failed to pull image with policy "always": Error response from daemon: manifest for python:3.8-stretch not found: manifest unknown: manifest unknown (manager.go:237:1s)
ERROR: Job failed: failed to pull image "python:3.8-stretch" with specified policies [always]: Error response from daemon: manifest for python:3.8-stretch not found: manifest unknown: manifest unknown (manager.go:237:1s)

A search on Docker Hub shows, that this tag does not exist: https://hub.docker.com/_/python/tags?page=1&name=stretch

Steps to Reproduce (for bugs)

Context

I used and tested python:3.8-bullseye in all stages of https://github.com/databrickslabs/dbx/blob/main/dbx/templates/projects/python_basic/components/.gitlab-ci.yml which worked nicely.

Your Environment

  • dbx version used: [dbx][2022-12-22 10:34:49.730] 🧱 Databricks eXtensions aka dbx, version ~> 0.8.7
  • GitLab Community Edition 15.6.2
  • Databricks Runtime version:
j-4 added a commit to j-4/dbx that referenced this issue Dec 22, 2022
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
e6a9b62
@j-4 j-4 linked a pull request Dec 22, 2022 that will close this issue
Open
4 tasks
j-4 added a commit to j-4/dbx that referenced this issue Dec 22, 2022
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
bcc7798
j-4 added a commit to j-4/dbx that referenced this issue Dec 22, 2022
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
e1b45f8
j-4 added a commit to j-4/dbx that referenced this issue Jan 12, 2023
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
c32d0d7
j-4 added a commit to j-4/dbx that referenced this issue Jan 12, 2023
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
357d550
j-4 added a commit to j-4/dbx that referenced this issue Jan 12, 2023
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
ce1df65
j-4 added a commit to j-4/dbx that referenced this issue Jan 12, 2023
@j-4
Uses python:3.8-bullseye for GitLab CI stages. Closes databrickslabs#647
1248e32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Uses python:3.8-bullseye for GitLab CI stages. j-4/dbx
1 participant
@j-4