Pankaj Nagla created SPARK-42033:
------------------------------------

             Summary: Docker Tag Error 25 on gitlab-ci.yml trying to start 
GitLab Pipeline
                 Key: SPARK-42033
                 URL: https://issues.apache.org/jira/browse/SPARK-42033
             Project: Spark
          Issue Type: Bug
          Components: Deploy
    Affects Versions: 2.1.1
            Reporter: Pankaj Nagla
             Fix For: 1.6.2


I'm going through the "Scalable FastAPI Application on AWS" course. My 
gitlab-ci.yml file is below.

    stages:
  - docker

variables:
  DOCKER_DRIVER: overlay2
  DOCKER_TLS_CERTDIR: "/certs"


cache:
  key: ${CI_JOB_NAME}
  paths:
    - ${CI_PROJECT_DIR}/services/talk_booking/.venv/

build-python-ci-image:
  image: docker:19.03.0
  services:
    - docker:19.03.0-dind
  stage: docker
  before_script:
    - cd ci_cd/python/
  script:
    - docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" 
$CI_REGISTRY
    - docker build -t 
registry.gitlab.com/chris_/talk-booking:cicd-python3.9-slim .
    - docker push registry.gitlab.com/chris_/talk-booking:cicd-python3.9-slim

My Pipeline fails with this error:

See 
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
$ docker build -t registry.gitlab.com/chris_/talk-booking:cicd-python3.9-slim .
invalid argument "registry.gitlab.com/chris_/talk-booking:cicd-python3.9-slim" 
for "-t, --tag" flag: invalid reference format
See 'docker build --help'.
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 125

It may or may not be relevant but the Container Registry for the GitLab project 
says there's a Docker connection error. All these problems have been discussed 
in this [Aws Sysops 
Training|[https://www.igmguru.com/cloud-computing/aws-sysops-certification-training/]]
 follow the page.

Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to