-
Notifications
You must be signed in to change notification settings - Fork 20
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
V2: Error 400 when doing update #117
Comments
Any logs from |
It seems that the containers disappeared:
|
logs from wazigate-edge:
|
Well yes, once a new update is downloaded, we delete all the current containers of the App and its images, then we re-install the app again. so at some point the container is not responding and since the log reading procedure (black box) is being run async to the update procedure in the background in one point this happens and it is ok. we just have to keep the JS errors for the dev console. |
OK, let's hide the error? |
Problem is, once the wazigate-lora is down, the docker will not restart it automatically. |
I retested, didn't see the error... Closing |
Can you please provide some logs? |
I got some logs on this error so when there is no docker image for a particular App on the gateway this error happens. Usually there is no way to get into this state, but when we flash a fresh ISO when LoRa App for example is installed, but the images somehow were pruned in ISO creation script while it should not. I am going to check why this happens. Here is the logs I got from the edge on updating an App generating this error:
|
Hi Moji, do you think this is fixed? |
I think yes I made sure the images exist on the ISO file. So when an update is initiated, this error should not appear. |
No, it looks good... Closing |
I got this error while doing an update:

The text was updated successfully, but these errors were encountered: