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

Does not support the port in the image name #280

Closed
corey-aloia opened this issue Jun 19, 2018 · 11 comments
Closed

Does not support the port in the image name #280

corey-aloia opened this issue Jun 19, 2018 · 11 comments

Comments

@corey-aloia
Copy link

if you write a from like this:

FROM repository.mycompany:5000/tomcat:8.0

then there will be an error "invalid reference format", with the 8.0 being underlined in red, although this is a valid statement.

@rcjsuen
Copy link
Contributor

rcjsuen commented Jun 19, 2018

Hi, @corey-aloia-sap. Thank you for your bug report.

It sounds very similar to #269 although your image is simply tomcat:8.0 and not something like apache/tomcat:8.0. It should still be fixed by rcjsuen/dockerfile-utils#39 though as I have a test for something very similar to what you have provided.

https://github.com/rcjsuen/dockerfile-utils/blob/4975fe383f809c16f944d6aec41aa87c6294a584/test/dockerValidator.test.ts#L2672-L2673

@corey-aloia
Copy link
Author

corey-aloia commented Jun 19, 2018

@rcjsuen yep, sorry about that! I could have looked through the open bugs a bit harder. Looks like the same issue.

rcjsuen pushed a commit to rcjsuen/dockerfile-utils that referenced this issue Jun 21, 2018
Another bug in the Microsoft/vscode-docker repository was opened
about this problem.

microsoft/vscode-docker#280

Signed-off-by: Remy Suen <[email protected]>
rcjsuen added a commit to rcjsuen/dockerfile-utils that referenced this issue Jun 21, 2018
Another bug in the Microsoft/vscode-docker repository was opened
about this problem.

microsoft/vscode-docker#280

Signed-off-by: Remy Suen <[email protected]>
@rcjsuen
Copy link
Contributor

rcjsuen commented Jun 21, 2018

Hi, @corey-aloia-sap. I wanted to let you know that I've confirmed that your issue has been covered by my fix for #269. I have added your sample Dockerfile to my test suite so it shouldn't regress in the future. Thanks again for the bug report! Have a nice day! :)

rcjsuen/dockerfile-utils@c9d2ad5

@lucianenache
Copy link

Hi, I didn't knew which issue to use between #269 and #280 so I have picked the later one. The same validation fails in case you use latest instead of the x.x.x version.

Example:
FROM my.private.repo.com:5000/some-image:latest

@rcjsuen
Copy link
Contributor

rcjsuen commented Jul 2, 2018

@lucianenache Thank you for your bug report. Your case is already covered by my fix in rcjsuen/dockerfile-utils#39. I have added your sample to my test suite nonetheless. Have a nice day!

rcjsuen/dockerfile-utils@36b99ae

@lucianenache
Copy link

lucianenache commented Jul 3, 2018

Thanks, for some reason under vscode I still get a linter warning even with the latest version of the plugin.
image

[dockerfile-utils] invalid reference format

@rcjsuen
Copy link
Contributor

rcjsuen commented Jul 3, 2018

@lucianenache Sorry for the confusion. The issue has been fixed upstream but the vscode-docker extension has not yet been updated to include this fix.

I will comment here when the fix has been adopted so please hang tight!

@Frodox
Copy link

Frodox commented Jul 12, 2018

subscribing for comments - new version released :)

@rcjsuen
Copy link
Contributor

rcjsuen commented Jul 12, 2018

The fix has been adopted as you can see in #291. However, a new release of vscode-docker will still need to be cut first.

@StephenWeatherford
Copy link
Contributor

@corey-aloia-sap I'm closing since this has been fixed in our repo. However, as @rcjsuen pointed out, the new version has not yet been released.

@StephenWeatherford
Copy link
Contributor

@corey-aloia-sap Just wanted to let you know that we have published a new version of the Docker extension that should contain this fix. Happy coding!

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants