Fix cache in Foxglove Studio #876
Replies: 3 comments
-
@rafal-gorecki Thanks for the detailed report. Would you be willing to make a PR to the https://github.com/foxglove/studio with your proposed fix? We can discuss the fix on the PR. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, now I have other responsibilities, and besides, I'm not an expert in these matters, so it's good for someone more advanced in the subject to take care of it, because perhaps it can be solved better and simpler. |
Beta Was this translation helpful? Give feedback.
-
Closing since we no longer maintain a docker image for open source. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Our team has identified an issue with the latest Docker image ghcr.io/foxglove/studio:latest (version 1.76.0). When running the image twice on the same machine with a modified default-layout.yaml, the layout does not update unless a new Chrome instance is opened in incognito mode. We've made some enhancements to your Docker image to address this issue, and we'd like to share our solution to assist in the development of your application.
Instructions to Reproduce the Issue
I. Empty Layout
compose.yaml
docker compose up
)localhost:8080
, and click "Open connection" with "Foxglove WebSocket".Result: You should see an empty layout.
II. Custom layout
docker compose down
)volumes
section in the compose file.docker compose up
)localhost:8080
in Chrome.Result: You should see an empty layout.
localhost:8080
.Result: The correct Foxglove layout should now be displayed.
Our solution:
We have addressed this issue in our foxglove-docker repository using the
ENTRYPOINT
directive. You can test our solution by following the steps outlined above with our compose file.We kindly share this change and ask you to include this change in the official Foxglove Docker image for a smoother user experience.
Best regards,
Rafał Górecki
Husarion
Beta Was this translation helpful? Give feedback.
All reactions