-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins 2.319.1 on Windows Server 2019
Docker Pipeline: 1.27
-
-
1.28
The update 1.27 of the docker plugin seems to have introduced a blocking issue.
When starting a container like so:
dockerImage = docker.build("${nexusDockerRegistry}/${DockerImageName}:${env.DISTRO_NAME}-windowsservercore-ltsc2019", "-f ${env.WORKSPACE}/${continuousDeliveryRepo}/deployment/docker/Dockerfile.bis ." )
I'm getting the follow error message in the log when using 1.27:
21:37:56 [Pipeline] withEnv 21:37:56 [Pipeline] { 21:37:56 [Pipeline] isUnix 21:37:56 [Pipeline] bat 21:37:57 21:37:57 user001@VM-NAME C:\jenkins\path>docker build -t "$JD_IMAGE" -f C:\jenkins\path/continuous-delivery/deployment/docker/Dockerfile.bis . 21:38:09 invalid argument "$JD_IMAGE" for "-t, --tag" flag: invalid reference format: repository name must be lowercase 21:38:09 See 'docker build --help'. 21:38:09 [Pipeline] }
After the downgrade to 1.26 I'm getting successfully usual messages:
08:30:23 [Pipeline] isUnix 08:30:23 [Pipeline] bat 08:30:23 08:30:23 user001@VM-NAME C:\jenkins\path>docker build -t registryMachine:8083/docker-image:docker-tag -f C:\jenkins\path/continuous-delivery/deployment/docker/Dockerfile.bis . 08:31:02 Sending build context to Docker daemon 690.4MB 08:31:02 Step 1/8 : FROM registryMachine:8083/docker-image:docker-tag ... etc ...
See also: JENKINS-67578
- is duplicated by
-
JENKINS-67603 invalid argument "$JD_IMAGE" for "-t, --tag" flag
-
- Resolved
-
- relates to
-
JENKINS-67578 No such object: $JD_TO_RUN
-
- Resolved
-