Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[regression] Confusion between image and repository + ":" + tag #68

Closed
guilhem opened this issue Jul 23, 2014 · 7 comments
Closed

[regression] Confusion between image and repository + ":" + tag #68

guilhem opened this issue Jul 23, 2014 · 7 comments

Comments

@guilhem
Copy link
Contributor

guilhem commented Jul 23, 2014

There is some confusion in code between this docker notions.

Before 0.7, it was not a problem as we can set image to repo:tag like guilhem/vagrant-ubuntu:14.04.
But it's not possible anymore because (in particular) of this line: src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java#L255 as it oblige tag latest (and fail if a : is given)

What we have to do is to add 2 new params, repository and tag.
If an image is given (a SHA) we can use it but can pull it.
If a repo + tag (by default "latest") is given, we can pull it if necessary.

I try coding it... it's over my java skills :(

@magnayn
Copy link
Contributor

magnayn commented Jul 24, 2014

I'm not sure that's a regression; DockerCloud:255 is new for this version, it's spinning up a container if one hasn't been found (though, now that I look at it, I'm not sure it's in the right place).

However, what you say is also true - it shouldn't assume that 'latest' is the one that's wanted. It should use Identifier to figure out which part is which, so ought to be a relatively simple fix.

@guilhem
Copy link
Contributor Author

guilhem commented Jul 24, 2014

Yes this is not exactly a regression, but it prevent from using a tag :) (who was working before).

@philpep
Copy link

philpep commented Jul 28, 2014

+1 To have tags working again (either via container ID parsing or a separate param)

@magnayn
Copy link
Contributor

magnayn commented Aug 4, 2014

I think you can work around if the slave already has the correct container..

@philpep
Copy link

philpep commented Aug 4, 2014

It doesn't seem. See my issue #70 , the image wheezy64:jenkins exists on the docker server, but it try to start wheezy64:jenkins:latest

@samrocketman
Copy link
Member

This appears to be fixed in docker plugin 0.8

@KostyaSha KostyaSha added the tag label Apr 23, 2015
@KostyaSha
Copy link
Member

i have "asdfasdf:b25" and it spins "asdfasdf:b25", probably issue resolved.
Please try #210 and reopen if it still reproduces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants