-
Notifications
You must be signed in to change notification settings - Fork 28
Can't build from source nor run from DockerHub #2
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
Comments
@marcellodesales Thanks for your question. My only thought is that this is an issue with the version of Docker that you are using. I'm using 1.5.0 here:
Under 1.5, I was able to run the image without problem. Didn't receive any issues when building either:
I'll try and spin-up a Docker 1.2 environment and see if I can re-pro your issue. |
Hi @bdehamer I upgraded my server to 1.6.2 and it's working...
However, there is no image being served... The screen still shows the empty information... I have confirmed that I have docker running...
Can you let me know if that's properly set? |
Hmm. Now I'm wondering if there isn't a browser problem. My log output here looks like this:
Note the call to Are you seeing any errors in the browser? Maybe in the developer tools console? |
I should probably point-out that we have a hosted version of this same tool now that is much easier to use: The primary difference is that the imagelayers.io tool allows you to inspect images on the Docker Hub instead of images in your local image cache. |
I'm aware of imagelayers.io, and I forked in the hopes to generate a hosted version of it... Couldn't get Ruby compiled with Node.js in Alpine yet... So, now I just want a quick way to visualize the images in a given host as we have an Internal registry... The current problem is on the server I guess :( |
@marcellodesales it does look like it might be something on the server side. Can you paste the output of running |
@bdehamer here it is!
|
@marcellodesales can I see your |
@bdehamer I'm really sorry :) I might have been sleepy :P Here they are...
|
@marcellodesales I'm still in the process of troubleshooting this (thanks for your patience). If possible, could you paste me the result of hitting the It should look something like this:
Thanks. |
@bdehamer So, the output is extremely long... It also took A LONG TIME to return... Here's the output of the second call...
I hope you can find clues from the output below... Or maybe because it is too long? JSON<elided> |
@marcellodesales The JSON you sent was super helpful. There are definitely a few entries in there that are causing the rendering problem:
Something about the data in the After removing those images, I was able to get the rest of the data to render without problem: I'll see if I can't figure out what it is about those images that is causing a problem and try to make a fix. |
I just pushed a new |
@bdehamer Perfect! I will double-check that... Ahh, those images were created for a tech session I gave last year... super old :) Not sure what's going on there, but I will remove them... I will check the fix first, and then remove the image and report back to you! thanks a lot for the help! |
It looks like those images were maybe built without using a Dockerfile (i.e. doing a |
I am using Docker on Fedora:
I am seeing the same error mentioned in this issue:
What could be the issue? |
Related with upserve/docker-api#415. |
I'm trying to run from DockerHub and I cannot generate anything... I have Docker 1.2 installed on my server...
Generate the local image
What version is this talking about?
Generating through the server...
Running is not working... Can you guys be more clear about the requirements? Is that the latest Docker?
Trying to build from github
thanks for any help!
Marcello
The text was updated successfully, but these errors were encountered: