-
Notifications
You must be signed in to change notification settings - Fork 1
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
Container trouble [Solved] #1
Comments
The What do you get if you run |
@jamesottaway Here is the output. I tried both because 8080 was not accepting any connections.
I see these logs when I cat the logs inside the container
I'm wondering if I maybe missed something in your steps. |
Looks like this might be a trovebox thing: photo/frontend#1572 |
That's weird that it's returning a HTTP 500 response from
Interestingly, though, it works fine in my browser here. You'll have to use the boot2docker IP, and port 8080, so try pulling it up in a browser that way and hopefully it will work. |
Wow that worked hitting it in the browser! I guess I should have tried that to begin with... Thanks for helping me troubleshoot this. |
Does this container still work?
I tried running this image following the instructions in the README but I get an empty page when I try to curl 127.0.0.1:80. (I ran this command from inside the boot2dockerVM) It looks like the files are on disk and when I check the nginx logs inside the container I see accesses but no errors. The index.php is pretty sparse. Is there another dependency I am missing besides this and linking mysql?
EDIT: For anyone that comes across make sure to visit the IP in the browser. For some reason that works. Curling from inside the container or from boot2docker does not, but visiting the boot2docker ip in the browser does.
The text was updated successfully, but these errors were encountered: