generated from caicloud/golang-template-project
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Ormb login 503 error #139
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/P0
Highest priority. Must be actively worked on as someone's top priority right now.
Comments
What's the version of harbor? /cc @simon-cj |
gaocegege
added
kind/bug
Categorizes issue or PR as related to a bug.
priority/P0
Highest priority. Must be actively worked on as someone's top priority right now.
labels
Oct 9, 2020
I use the latest version of harbor via helm chart from here
|
I tried to login using ormb 0.0.6 and latest harbor, it works: ormb login --insecure 10.227.73.xx
Username: admin
Password:
Login insecurely
INFO[2020-10-09T09:45:55+08:00] Error logging in to v2 endpoint, trying next endpoint: Get "https://10.227.73.xx/v2/": dial tcp 10.227.73.xx:443: connect: connection refused |
We are using harbor v2.1.0, you can using http(--insecure) and try again @xieydd |
I use nginx pod ip and https port, it works.
But i meet other problem , why find
|
- ./bin/ormb push ./examples/PMML-model 172.16.93.122:8443/ormb/pmml:v1
+ ./bin/ormb push 172.16.93.122:8443/ormb/pmml:v1 |
haha, my mistake. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/P0
Highest priority. Must be actively worked on as someone's top priority right now.
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
when i login with ormb, it will be 503 error, log is below:
What you expected to happen:
ormb login sucessful
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
docker login is ok
The text was updated successfully, but these errors were encountered: