Hi @Antarr Byrd and welcome to the community!
Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. If you use a service for a step, then a second Docker container will start for the service which will share a network adapter with your build container. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes the Docker containers get destroyed.
We have a guide for debugging pipelines builds locally with Docker:
I would suggest following this guide to debug your build locally and see if the issue is reproducible. When debugging locally, please make sure that you use the same Docker images as in your bitbucket-pipelines.yml file (ruby:2.7.8-slim-bullseye for the build container and mysql:8.0.26 for the service container).
If the issue is reproducible locally, then the error is not specific to Pipelines (it may be related to the Docker image of the build container or your source code). When debugging locally, you can also run additional commands to troubleshoot this further. You could also try debugging it locally with different Docker images.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.