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

Improvement: Improve vague/unhelpful error message when container name is not recognized #39237

Open
ORESoftware opened this issue May 19, 2019 · 0 comments
Labels
area/ux kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.

Comments

@ORESoftware
Copy link

ORESoftware commented May 19, 2019

I have this question on SO:
https://stackoverflow.com/questions/56203979/docker-run-invalid-reference-format?noredirect=1

I am getting this error:

docker: invalid reference format.
See 'docker run --help'.

I have this:

docker run --rm   \
    "$ecr_endpoint/notifier-cli:latest"                \
    --build-exit-code "$exit_code"                     \
    --event 'build-end'

the exit status of the docker run command is 125, if that helps. I have no idea what's going on here...an identical command is running fine earlier in the script.

so if the $ecr_endpoint variable was empty, then the docker run program likely saw this:

docker run --rm /notifier-cli:latest  ...

so maybe the error message could be improved somehow? an improved error message would help people - docker run should know that it's an image that doesn't exist, since nothing is expected after the --rm arg...right.

@thaJeztah thaJeztah added kind/enhancement Enhancements are not bugs or new features but can improve usability or performance. area/ux labels Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ux kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.
Projects
None yet
Development

No branches or pull requests

2 participants