I updated my docker-plugin to 1.1.2 also. On Tuesday, December 19, 2017 at 10:11:29 AM UTC-6, nicolas de loof wrote: > > JENKINS-48490 is not implemented in jenkins-core but docker-plugin, and > should be fixed in 1.1.2 > > 2017-12-19 16:18 GMT+01:00 Mandy Hubbard <[email protected] > <javascript:>>: > >> JENKINS-48490 is fixed in 2.89.1. I upgraded to 2.89.1 and am still >> seeing the issue. I plan to open a new defect for this. >> >> On Monday, December 11, 2017 at 5:32:05 PM UTC-6, Mandy Hubbard wrote: >>> >>> Thanks for the reply, Nicolas. Can't say it is the response I was >>> hoping for but at least I know it's not just me. I've had it working many >>> times before so I knew I had configured it correctly. Any hints for >>> working around this for now? I tried restarting Jenkins but it didn't >>> help. >>> >>> On Monday, December 11, 2017 at 2:24:08 PM UTC-6, nicolas de loof wrote: >>>> >>>> sounds to me this is more or less >>>> https://issues.jenkins-ci.org/browse/JENKINS-48490 >>>> which is a recurrent issue. Still looking for a definitive fix >>>> >>>> >>>> 2017-12-11 17:49 GMT+01:00 Mandy Hubbard <[email protected]>: >>>> >>>>> Using the Docker Plugin to run Jenkins agents in containers, I often >>>>> get the error "Jenkins doesn't have label <agent label>" even when I have >>>>> the template configured properly and the Docker image is already present >>>>> on >>>>> the Docker host. I have sometimes been able to fix it by removing the >>>>> image and re-pulling it to the host but at other times I am completely >>>>> stuck. I've tried it using a tag and with no tag. Has anyone else run >>>>> into this? Do you have any hints on what it could be? >>>>> >>>>> Job run log says: >>>>> >>>>> Still waiting to schedule task >>>>> Jenkins doesn’t have label python >>>>> >>>>> >>>>> Here's my docker image >>>>> jenkins@b1e2e4c28dbd:/$ docker images >>>>> REPOSITORY TAG IMAGE ID >>>>> CREATED SIZE >>>>> devmandy/python-jenkins-agent 1 6cc6f98875bc 2 >>>>> hours ago 991MB >>>>> >>>>> A screenshot of my Jenkins config is attached. >>>>> >>>>> >>>>> -- >>>>> 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/bd8e173f-844b-4b48-9ba6-56df650b0868%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/bd8e173f-844b-4b48-9ba6-56df650b0868%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/82b914ce-695e-47ba-aaac-041afcc6a7f6%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/82b914ce-695e-47ba-aaac-041afcc6a7f6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > >
-- 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/fa4fa9d9-3c32-4eb6-a78a-434c69ac5e5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
