You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running 2 container on my device where Container A is a MQTT Service and Container B is using this service via a client. (like explained in the service examples).
If I am installing the two containers they are running fine. But once I update container A, Container B still has a reference to the previous Service of Container A and somehow the update of Container A did not re-new this reference by e.g. restarting container B.
Container B will be in a state which shows the error "NO_SUCH_PROCESS" if it tries to talk to its service.
Is there a way to make Container B dependant on Container A so once this gets updated, Container B will be restarted as well?
Or maybe simply just reset the device after an update of a container?
This was using Jaguar, how is that handled in Artemis? I assume I would run intoi the same issue there, right?
Thats seems to be a problem especially for services which gets installed using a provider and other containers using this service.
The text was updated successfully, but these errors were encountered:
I am running 2 container on my device where Container A is a MQTT Service and Container B is using this service via a client. (like explained in the service examples).
If I am installing the two containers they are running fine. But once I update container A, Container B still has a reference to the previous Service of Container A and somehow the update of Container A did not re-new this reference by e.g. restarting container B.
Container B will be in a state which shows the error "NO_SUCH_PROCESS" if it tries to talk to its service.
Is there a way to make Container B dependant on Container A so once this gets updated, Container B will be restarted as well?
Or maybe simply just reset the device after an update of a container?
This was using Jaguar, how is that handled in Artemis? I assume I would run intoi the same issue there, right?
Thats seems to be a problem especially for services which gets installed using a provider and other containers using this service.
The text was updated successfully, but these errors were encountered: