-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Docker login fails on Travis #471
Comments
The problem only occurs on branches which are in a fork. I will update the travis config soon, what is there right now was just to get automated build and push working and I hven't had the time to clean everything up yet.
… On Feb 22, 2018, at 7:31 AM, Zsolt Ero ***@***.***> wrote:
@Theaxiom <https://github.com/theaxiom> the new travis config fails to log in to docker, docker login is actually waiting at a
"Username:" prompt forever and then gets cancelled after 10 minutes.
Maybe the travis version still requries the -e email switch as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#471>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADetUZ6daRwUcTMd5Bno-uvREIfJNuOks5tXYhjgaJpZM4SPgPy>.
|
any update on this ? |
Yeah, it is very annoying. I am going to be fixing it shortly. Thanks for your patience! |
Closed
Apologies everyone for my lack of attendance, I've been really consumed by life lately. I have upgraded @kingdonb to admin along with @hyperknot -- I appreciate both of your help in maintaining this project! Thank you! I will eventually fix the Docker stuff, unless someone gets to it first. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@Theaxiom the new travis config fails to log in to docker, docker login is actually waiting at a
"Username:" prompt forever and then gets cancelled after 10 minutes.
Maybe the travis version still requries the -e email switch as well?
The text was updated successfully, but these errors were encountered: