Repository navigation
test(nuxt): Pin the nuxt-5 e2e MongoDB image to 8.0 - #25564
Merged
Merged
Conversation
Same fix as #25557 for nuxt-4. The floating `mongo:8` tag now resolves to 8.3, whose server sometimes exits right after start on CI, so `docker compose up --wait` reports the container as unhealthy. Also print the container logs when setup fails.
s1gr1d
marked this pull request as ready for review
October 20, 2026 14:19
logaretm
approved these changes
Oct 20, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Same fix as #25557, applied to nuxt-5. It failed the same way on #25552 (
container e2e-tests-nuxt-5-mongo is unhealthy)The floating
mongo:8tag moved to 8.3 on 2026-10-17. On CI the container goes unhealthy some seconds after start. That is much earlier than the healthcheck retries allow, so the server process exits, and Docker then reports the container as unhealthy. If setup fails again, the container logs now print, so we can see why mongod exits.