-
Notifications
You must be signed in to change notification settings - Fork 27
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 container crashing on lauch #269
Comments
I can't really help here as I haven't used Docker that much. This feature was added by another contributor. |
@haeferer do you know where this issue is coming from? |
I think its the same problem as #261 or #265 try to add this line to your docker file (I think you has used another Checkout ID, so these files a needed now ?)
|
No I am using c182732 as checkout id. |
correct, in this version the command was "update-firmware": "node ./node_modules/spark-protocol/dist/scripts/update-firmware-binaries", so please try this. I cant explain why the image crashes, cause this is the same checkout as i used. |
I now get the following error:
But I have already setup a .env file with credentials. I don't understand why either. |
... ( ??? Sounds strange. I will try to setup a test, but this could take some time (the project is currently at hold). |
Oh yeah when scrolling up I have two other error, but nothing in link with the checkout though.
and
|
This sounds strange (maybe the alpine Image - pined at version 7) has changed. If you look at my last commit da7d9ad i've changed the Dockerfile from Alpine-Node6 to Alpine-Node7. And all the gyp and phyton dependencies could be removed (at this time) now the same dependencies are missing again ???? you are using the correct dockerfile (without any changes?) are you using docker on windows or linux |
I am using the correct Dockerfile with only the update firmware line added. I am using Docker on Linux. |
I managed to overcome the initial error by creating a settings.json file in node_modules/spark-protocol/third-party with: I have a new error though...
|
@yannick-mayeur - that really sounds like you didn't set the correct server key before running |
I don't know why it behaves like that but when I restart the docker container it works. I was able to reproduce the bug with another docker image. |
@yannick-mayeur - I'm guessing we've fixed this with recent changes to the way we pull system firmware. I'm not sure if the docker image needs to be updated. |
When I am running the docker container built with the Docker file in ./examples/docker/production I get the following error:
The text was updated successfully, but these errors were encountered: