Gateway / designer sync errors using containers

I am getting periodic sync issues between my GW and designer where a warning appears that a GW/Designer conflict has been found with the designer resource i am working on.

The conflict dialog box shows that the resource no longer exists in the GW, so i choose to keep the update from the designer. unfortunately this only works if i happen to have the resource open in the designer, if not, the GW version is automatically preferred and the resource just disappeared from the designer, never to be seen again.

I am working from a GW hosted in a container that has been set up by a 3rd party, and unfortunately I am not very familiar with containerization. Has anybody come across this issue before?

This sounds like a problem with the docker setup itself. Your Ignition Gateway itself will be accepting updates from the designer like normal.

A few questions come to mind

  1. Are you able to save changes at all?
  2. Does this happen every time you try to save
  3. When you do save, are those changes reflected in the view?

What may be happening is the container isn't properly setup, and although the designer can see and is connected, the traffic for your save may be getting lost, or they are doing some weird backup/restore in the container that is overwriting changes. Docker is a great tool, but when setup wrong it is the biggest headache.

1 Like

Thanks for your response, it definitely was an issue with the container, but it appears to be resolved for now. Not sure exactly what the cause was, I but was told it was related to the memory available to the container. In answer to your questions:

  1. Yes other changes such as creating new folders and bindings were being saved.
  2. No it didn't appear to be triggered by saving, but would appear periodically
  3. Yes

I will be monitoring closely to see if the problem reappears, but for now it is working.

1 Like