So what values do you put in your cloud section of you Jenkins config page for the 'Task definition' and 'Docker image' fields?
[image: Screen Shot 2019-04-16 at 11.05.13 AM.png] On Friday, April 5, 2019 at 2:21:10 PM UTC-4, Ivan Fernandez Calvo wrote: > > We have a similar problem, to make a local cache of those images we pull > then when we build packer images (once a day) so when we spin our VMs they > have those Docker images and don't have to pull them from any repository. > The only disadvantage of that it is you need extra disk space. In your > case, you can do the same if you build your own AMIs > > El viernes, 5 de abril de 2019, 16:59:22 (UTC+2), ZillaYT escribió: >> >> We have a number of EC2 instances that we create in our AWS ECS cluster, >> which run Docker. One of the EC2 instances run the Jenkins master, and the >> others are designated as slaves. >> >> So what we do is for every job, we run a Docker container in one of these >> slave EC2 instances. We set up, in the Cloud portion of Jenkins >> configuration page, a label called 'linux-fargate' that has the task >> definition and the Docker image that we want to run. >> >> All is working well, that is, we are able to run a Docker container for >> each job using the task definition and Docker image we set up in the >> configuration page. >> >> However, we pull the image from our ECR repo "every time" and this takes >> a long time. How can we tell Jenkins to use the image that's already on the >> EC2 instance instead of pulling the image every time? >> >> Thanks, >> Chris >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/502186ce-4ddf-402e-9a64-13e28ee29612%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
