[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Michael Kühn commented on JENKINS-50593 Re: Docker image from private registry is ignored in the global container template configuration Thanks, everything works as designed. The mistake was ours. The correct template was not used. There was a fault in the template name and six eyes didn't see it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Michael Kühn closed an issue as Postponed User fault Jenkins / JENKINS-50593 Docker image from private registry is ignored in the global container template configuration Change By: Michael Kühn Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title
Michael Kühn created an issue
Jenkins / JENKINS-50593
Docker image from private registry is ignored in the global container template configuration
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
2018-04-05_14-48-49.jpg
Components:
kubernetes-plugin
Created:
2018-04-05 14:34
Environment:
jenkins: 2.107.1 kubernetes-plugin: 1.5 kubernetes: 1.9.2
Priority:
Major
Reporter:
Michael Kühn
In the global jenkins configuration we define the jnlp container template with an image from our own registry (jenkins/jnlp-slave:3.16-1). When a job is started it is always tried to load the jenkins/jnlp-slave:alpine image. It seems that our image definition is ignored. Apr 5 09:17:07 epdl9415 kubelet: I0405 09:17:07.819436 193036 kuberuntime_manager.go:514] Container {Name:jnlp Image:jenkins/jnlp-slave:alpine Command:[] Args:[02f3888416
