Closed Romariin closed 1 year ago
We shouldn't roll back the master branch to an older version, but I do agree that we should have an automated build that tracks the stable
(recommended) build versions.
For now, I've built 5848 based on your PR and pushed it to DH for you https://hub.docker.com/layers/spritsail/fivem/5848/images/sha256-a5dd639689824d5195d193bf8508cd2587c5b947781105c555329976e6b6e0be?context=explore
We can look at adding those extra builds later. I hope this is sufficient for now. Let me know if not
@frebib Perfect 👌 Thanks !
Maybe there's a problem, the containers don't want to get started. (No errors logs)
Worked well on tag 5963
Could this be due to the DATA_VER
that I didn't change in my version?
139 is segmentation fault. I wonder if the data is incompatible like you say. Is there any reason you want this really old build btw?
139 is segmentation fault. I wonder if the data is incompatible like you say. Is there any reason you want this really old build btw?
There's no need, the recommended artifacts recently changed to 6683, and the build is in the tags (here). Thanks a lot anyway for the help, and sorry to have bothered with this 😅
Hello ! 👋 I didn't see the tag 5848 (latest recommended artifacts) in https://hub.docker.com/r/spritsail/fivem/tags
This pull request may fixes the problem! Have a nice day! 😎