-
Notifications
You must be signed in to change notification settings - Fork 240
Something wrong with your containers #5
Comments
@icinsight Did you give it enough time to boot up? You can get a 403 error if you try to access Launch Kit before Docker fully loads. Can you give details on OS, browser, Launch Kit spec, etc? |
@tomhschmidt @fabioberger perhaps a default Also seems like we re-build on every docker-compose up, even if the code hasn't changed. Which means this issue persists even after the first (long) build. Subsequent builds on my laptop take close to a minute. |
Yes, a default
I don't know if there's a good way of avoiding the re-builds, since that is necessary to let the user configure the environment variables. I mean, that is done in the |
Everything is up and running nicely, and I can see the back-end trying to serve the browser in port 3001, but the html file that it is trying to send has a permission issue. I set up and launched everything as root so that may cause the issue. I'll try again. |
@icinsight that shouldn't be a problem. What is happening is that the app is being built, and that takes some time (about a minute). Try this: run
When that happens, go to |
Third time now; works fine. Thanks! |
I get "403 Forbidden nginx/1.15.12 error"
nginx_1 | 2019/05/30 02:23:55 [error] 6#6: *7 directory index of "/usr/share/nginx/html/" is forbidden, client: 24.215.98.192, server: localhost, request: "GET / HTTP/1.1", host: "138.197.145.222:3001"
nginx_1 | 24.215.98.192 - - [30/May/2019:02:23:55 +0000] "GET / HTTP/1.1" 403 556 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36" "-"
The text was updated successfully, but these errors were encountered: