Giters

odigos-io / odigos

Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF

Home Page:https://odigos.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No up-to-date image available for odigos UI on dockerhub

thomaspetit opened this issue · comments

commented

Is your feature request related to a problem? Please describe.

There are docker images available for odigos on dockerhub:
https://hub.docker.com/r/keyval/odigos-ui/tags

Following images have all been updated to v1.0.2:
keyval/odiglet-base
keyval/odigos-cli
keyval/odigos-odiglet
keyval/odigos-instrumentor
keyval/odigos-scheduler
keyval/odigos-autoscaler

While odigos-ui has not been released yet.

Describe the solution you'd like
Push a v1.0.2 image of odigos-uiunder the keyval account on dockerhub

commented

@edeNFed it seems I'm having difficulty to even build the latest frontend, am I missing something?

commented

Attempted to test. Much of the documentation for the UI provided in the quickstart is wrong. OTEL and elastic providers are do not even show

commented

I had some opportunity to work on it too past days (during spare time on conference). It seems to me that this dockerfile that we provisioned in the frontend folder was completely incorrect. So far I've refactored already 50% to make it work and run the code. Locally I can get it to work (without containers) but I came to pretty much the same conclusion.

It's really weird.. Feels like things were rushed and not checked in? 😨

commented

Hi @thomaspetit can you please let me know what is the problem with the current Dockerfile?
I can build it successfully by executing:

docker build -t dev/frontend:dev . -f frontend/Dockerfile

from the root directory of the Odigos repository. Also seems like GitHub action is also working

commented

@edeNFed I've wiped my podman vm (deleting all my images) and wiped the git repo I cloned locally and confirm it now builds. Among many issues, this was one of them:

TS2786: 'ThemeProvider' cannot be used as a JSX component.
Its instance type 'Component<ThemeProviderProps<any, any>, any, any>' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
commented

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

commented

This issue was closed because it has been stale for 30 days with no activity.