Arch Linux User Repository

Hi, thanks for the fix. It is working now.

I think I found the issue. It's not well documented, but some static assets have to be built in addition to setting the builtinassets go tag. I believe the changes in 1.11.2-3 should work.

I have checked 1.11.2-2 and the problem is still visible. In particular I had already the docker installed, so adding it to makedepends haven't changed anything in my build environment.

Hi @lekcyjna, thanks for the report! Would you please let me know if you experience the same issue with 1.11.2-2?

Hi @bschnei, I have found that alloy build from this AUR script have not working UI. When I try to open http://127.0.0.1:12345/ as described in official documentation[1] I get "404 Not Found". I have checked with strace and I have found that alloy looks for a path "internal/web/ui/build":

read(8, "GET / HTTP/1.1\r\nHost: 127.0.0.1:"..., 4096) = 468
openat(AT_FDCWD, "internal/web/ui/build", O_RDONLY|O_CLOEXEC) = -1 ENOENT
write(8, "HTTP/1.1 404 Not Found\r\nContent-"..., 176) = 176

This path does not exists after AUR build. I have found that some references are in alloy Dockerfile[2] (lines 7-13 and 29), where a yarn is used to build something in "internal/web/ui" and next "build" subdir is copied to the Docker image. I have build the required files with yarn and tried to start alloy from the root dir of alloy repo (so that relative path "internal/web/ui/build" will be correct) and the UI started to work.

I am not sure how to apply a fix to the PKGCONFIG as I am not a go user, but in "ui.go"[3] file from alloy repo there is a comment about adding "builtinassets Go tag" to embed these files into binary.

With best regards, Lekcyjna

• [1] https://grafana.com/docs/alloy/latest/troubleshoot/debug/
• [2] https://github.com/grafana/alloy/blob/2482d9d4ac8312ddf51d6ec10c3cbbb82de8d53e/Dockerfile
• [3] https://github.com/grafana/alloy/blob/2482d9d4ac8312ddf51d6ec10c3cbbb82de8d53e/internal/web/ui/ui.go#L24

Hi @hexchain, thanks! As I indicated in my response to @bone below, it would be great if this were made clearer in upstream documentation. Their documentation does already make a distinction between which build-time dependencies are needed only in specific cases[0]. They may have other reasons for wanting it to always be installed even if it is not currently used by the "default" build instructions. If you can either confirm with upstream that it is intended to only be an optional dependency, or, even better, make their documentation clearer, I'd be happy to make the change. Thanks!

[0] https://github.com/grafana/alloy/blob/v1.8.1/docs/developer/contributing.md#compile-on-linux

Building Alloy using the system-wide Go toolchain should not (and does not) require Docker. The Makefile uses Docker when invoked with USE_CONTAINER=1, or when building an image, neither of which is the case here.

Hi @bone, thanks for your note! I can confirm v1.8.1 appears to build without it on x86_64, but upstream documentation[0] explicitly lists docker as a build-time dependency. I do not know their reasoning, but unless/until they remove it from their guide (or clarify if it is architecture/OS specific), I'm inclined to keep it to avoid breaking some case I cannot test (e.g. aarch64). In other words, if you determine the issue is with the upstream contributor guide, I'd prefer that gets fixed first so that all distributions might benefit.

[0] https://github.com/grafana/alloy/blob/v1.8.1/docs/developer/contributing.md

This package builds just fine without the docker make dependency. Would you mind removing it from the build dependencies?

@TheTaktik added in 1.5.1-2