[Cmake] [Docker] Issue when using docker-compose

[caiopolito]

Priority

High

Area

• Datapack
• Source
• Map
• Other

What happened?

Hi everyone :D

Just recently, with this LuaJIT problem everyone's been facing, I've started trying to deploy a version of a server with the docker tools available on the canary package, but even with the latest version, I've been having trouble with the docker-compose, when building all vcpkg packages. When the console gets to libmariadb, it breaks with the following messages:

#13 151.9 Call Stack (most recent call first):
#13 151.9 vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:238 (vcpkg_execute_required_process)
#13 151.9 ports/libmariadb/portfile.cmake:40 (vcpkg_cmake_configure)
#13 151.9 scripts/ports.cmake:147 (include)

#13 151.9 error: building libmariadb:x64-linux failed with: BUILD_FAILED
#13 151.9 Please ensure you're using the latest port files with 'git pull' and 'vcpkg update'.

All my canary docker files are up to date with the main branch of the project. My OS is Windows 10. I've made no modifications to this reproduce this problem, so I believe is something generic.

Has anyone had this problem too?
If so, is there any hotfix I can do?

What OS are you seeing the problem on?

Windows

Code of Conduct

• I agree to follow this project's Code of Conduct

[beats-dh]

@caiopolito I haven't tested it yet but very likely we will have to revert this commit: https://github.com/opentibiabr/vcpkg/commit/581099d541ec960db5c2a8efe4639f1e2e25de60

[caiopolito]

@beats-dh One thing that I've noticed here, is that the server's dockerfile is actually pulling directly from Microsoft, and not from this repo that you've mentioned. I'll try reverting this commit to see if it has any effect.

[beats-dh]

@beats-dh One thing that I've noticed here, is that the server's dockerfile is actually pulling directly from Microsoft, and not from this repo that you've mentioned. I'll try reverting this commit to see if it has any effect.

You can change the link to our fork in the docker file, revert the commit and if it works, you can open PR us 2

[github-actions]

This issue is stale because it has been open 120 days with no activity.

[murilo09]

Fixed in #716