Bug: pipeline.index J.randomUUID is not a function about conduit HOT 12 OPEN

@MichalisDBA I've just tried with AlmaLinux 9.4 in a Docker container, and it works. It could be very well an issue related to the version of the browser you're running (mine is Firefox 126.0.1 and Vivaldi 6.7).

from conduit.

Hi @hariso. Try it without docker. Just install the rpm package with the binary files. I do not use docker. Also tried it with Firefox and Edge. Same problem.

Tried with latest versions of Firefox, Edge, Vivaldi without docker. Only the binary file from .rpm or tar.gz packages.

from conduit.

I installed Conduit using a Debian package as well, and it works... Do you mind running Conduit with docker run -p 8080:8080 ghcr.io/conduitio/conduit and trying it out that way? Personally, I doubt the OS/installation method matters much.

from conduit.

I have RHEL based Linux systems. Almalinux is one of them. The thing is conduit has binary files that you can run but they are not working on RHEL Clone systems as it seems. Docker image maybe is based on debian that's why on debian and on docker it runs.

They thing is they need to fix their binaries for other systems or else pull them from the release page.

from conduit.

Also i tried and build the binary file from source. Same error in console from the build binary file.

from conduit.

I'm from the Conduit team, I'll try to help as much as possible. What version of Go and yarn were you using when you built Conduit?

I ran Alma Linux 9.4 in a Docker container (and I don't expect it to have significant differences versus a "normal" Alma Linux installation). Then I installed Conduit following the steps you provided (wget, rpm -ivh), and it worked.

I also modified our existing Dockerfile (that builds Conduit from source) to use Alma Linux 9.4, and that worked too. So I'm sure there's something more to it.

from conduit.

I run Alma Linux 9.4 in a VM not as a docker container, minimal installation. You have to try it in a VirtualBox or some else virtualization software. Maybe your situation works because alma linux docker container shares some things with the host machine you run it, for example debian.

I test in on a clean Alma Linux 9.4 installation in VirtualBox. Latest version of GO 1.22 and YARN

from conduit.

Clean installation

Run ./conduit

Try to Create Pipeline

from conduit.

Hmm, I don't think a Docker container is supposed to share anything with the host (unless you explicitly tell it, which we don't).

How about NodeJS, which version of it are you using?

from conduit.

Also, when you get to it, can you please share the output of yum list installed?

from conduit.

I can give you access to a fresh VM in Hetzner running AlmaLinux 9.4 to try for youself. Is there a contact info to send you the SSH login?

from conduit.

Hi @MichalisDBA! Sorry you ran into this issue 😔. Until we find the culprit of this UI bug, could we maybe help you get started with your pipeline using a pipeline configuration file instead?

Steps involved would require not using the UI, so I hope you are comfortable there.

from conduit.