Docker-Compose fresh install minor issue #1320
Assignees
Labels
component/api-server
defect
Something isn't working
p2
Non-critical bugs, and features that help organizations to identify and reduce risk
size/S
Small effort
Comments
2 tasks
Are all containers up and healthy when this happens? There will be a slight delay at first, since the API server depends on multiple containers being healthy: Lines 127 to 133 in 224540c And those containers have healthchecks with 5s intervals: Lines 174 to 178 in 224540c Lines 208 to 212 in 224540c
Good catch, I raised #1321 to fix it. |
|
Yes, all containers are healthy and up. I have waited 5 minutes after starting the containers to check the issue again. It still there |
|
Ah I think I found the issue. When you look at the API server logs, is it stuck at this line? I think we need to tweak how the API server is waiting for topics to be present. |
nscuro
added
p2
nscuro
added a commit
to DependencyTrack/hyades-apiserver
that referenced
this issue
Jun 11, 2024
Prevents the API server from getting stuck while waiting for Kafka API responses. Fixes DependencyTrack/hyades#1320 Signed-off-by: nscuro <[email protected]>
2 tasks
Here is the log output |
|
Thanks for the logs. Looks like that's the issue I meant. There should be further logs from |
|
Reopening, that didn't help. For some reason the request to describe topics of the cluster gets stuck, despite various timeouts being configured: Might be a bug in Kafka's |
|
I can only reproduce this on an arm64 MacBook, but not on a similarly specced amd64 Linux machine. Really odd. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
I am running hyades via docker-compose as described in the quick start guide:
docker-compose --profile demo up -d --pull alwaysBy default it uses arm64 images which match to my mac archetecture. I did not check if this issue exists on x86_64 images.
On the first run frontend returns 503 http error during login
But once I execute
docker-compose --profile demo downanddocker-compose --profile demo up -d --pull alwayseverything works fineAdditionally, Postgres healthcheck does not work properly on arm64
It continuously echoes
FATAL: role "root" does not exist. I did not check if this issue exists on x86_64 images as well.Steps to Reproduce
Make a fresh installation of hyades:
docker-compose --profile demo downdocker-compose --profile demo up -d --pull alwaysExpected Behavior
Login should work on the first run
Hyades Version
Versions are hardcoded in the docker-compose file - https://github.com/DependencyTrack/hyades/blob/601d221dfd7e277007b75b70d12c9d1e9ea948f8/docker-compose.yml
Repository Type
Hyades services
Browser
Google Chrome
Checklist
The text was updated successfully, but these errors were encountered: