Is it possible to use a non-default bridge network when running CodeBuild locally?

When running AWS CodeBuild locally, it automatically creates default Docker resources such as networks and volumes to facilitate the build process. However, if you need to use a different bridge network and volumes, you typically need to ensure that the containers in your local environment, including localstack, can communicate with each other over the desired network.

Here are steps and considerations to configure CodeBuild to use a different bridge network and volumes:

Using a Different Bridge Network

1. Create a Docker Network: Before running CodeBuild locally, create a custom Docker bridge network that both CodeBuild and localstack containers can connect to. For example:

docker network create mylocaltestingnetwork

2. Modify CodeBuild Invocation: When invoking CodeBuild locally using the codebuild_build.sh script, ensure to specify the custom network with the --network option. Update your command to include this network specification:

./codebuild_build.sh \
    -i public.ecr.aws/codebuild/amazonlinux2-x86_64-standard:3.0 \
    -a codebuild-output/ \
    -b buildspec-local.yml \
    -c \
    -p localstack \
    --network mylocaltestingnetwork

3. Ensure Network Accessibility: Verify that both CodeBuild and localstack containers can access the mylocaltestingnetwork. This might involve configuring your localstack services or any other containers to connect to this network explicitly.

Using Different Volumes If you need to use different volumes:

Create Docker Volumes: Similarly, create Docker volumes as needed before running CodeBuild:

docker volume create my_source_volume
docker volume create my_user_volume

Modify CodeBuild Invocation: Update your codebuild_build.sh script or command to mount these volumes:

./codebuild_build.sh \
    -i public.ecr.aws/codebuild/amazonlinux2-x86_64-standard:3.0 \
    -a codebuild-output/ \
    -b buildspec-local.yml \
    -c \
    -p localstack \
    -v my_source_volume:/path/to/source \
    -v my_user_volume:/path/to/user

Volume Accessibility: Ensure that the paths and permissions for these volumes are correctly set up and accessible by both CodeBuild and localstack containers.

Additional Considerations to take note of :- Network and DNS Resolution: Ensure that containers in your custom network can resolve each other's hostnames or IPs as needed, especially if there are dependencies or services that rely on name resolution.

Security Groups and Firewalls: Check if any security groups or firewall rules on your host machine or Docker daemon might restrict network communication between containers.

By following these steps, you should be able to configure AWS CodeBuild to use a custom Docker bridge network and volumes for your local development environment, ensuring compatibility with localstack or other services as required. Adjust configurations as necessary based on specific networking requirements and constraints of your local setup.