๐ Use debian base image to allow usage of odiff
Odiff isn't ABI compatible with musl-libc (alpine) and thus causes crashes when called. Where as debian uses gnu-libc which is compatible with the odiff binaries.
๐งน Remove deprecated docker compose file version
๐ค Also use debian base image for migrations? (consistency)
Using the same base image for migration and the API might reduce debugging afford for bugs related to prisma alpine/debian differences (i.e. binaryTargets)
๐ฉน๐ Use docker compose v2 CLI call in workflow
This fixes the error: "docker-compose: command not found"
Odiff isn't ABI compatible with musl-libc (alpine) and thus causes crashes when called. Where as debian uses gnu-libc which is compatible with the odiff binaries.
Ref.: https://github.com/compose-spec/compose-spec/blob/main/spec.md#version-and-name-top-level-elements
Using the same base image for migration and the API might reduce debugging afford for bugs related to prisma alpine/debian differences (i.e. binaryTargets)
This fixes the error: "docker-compose: command not found"