CI: Fix docker ci job not checking if Invidious starts successfully or not #5306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
syeopite
requested changes
May 15, 2025
Fijxu
force-pushed
the
fix-build-docker
branch
3 times, most recently
from
7fadbd5 to
01c6c2e
Compare
syeopite
approved these changes
May 15, 2025
Fijxu
force-pushed
the
fix-build-docker
branch
2 times, most recently
from
ffa8de5 to
2a8d690
Compare
unixfox
approved these changes
May 18, 2025
syeopite
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #5305
As discussed on #5305 (comment), we noticed that the
build-dockerjob doesn't actually checks if Invidious works or not, because curl always exited with code0(success) and the current docker-compose.yml files has defaults that will make Invidious fail at start (hmac_keymissing).