Run Codebuild Image locally using Docker(Powershell Terminal)

When running AWS CodeBuild locally using Docker on a Windows machine with PowerShell, there are a few things to consider to ensure that changes to your buildspec.yml file are reflected in subsequent builds.

First, make sure you're using the correct path format for Windows when specifying volume mounts. In PowerShell, you should use forward slashes (/) or escaped backslashes (\) for paths.

To address the issue of changes not being reflected, you can try the following:

1. Ensure that you're mounting the correct directory containing your buildspec.yml file. In your command, you're mounting "//C/dev/codebuild" as the source. Make sure this path is correct and contains your updated buildspec.yml.

2. Instead of relying on the default buildspec.yml, you can explicitly specify the buildspec file to use. Add the following environment variable to your docker run command:

   -e "BUILDSPEC=//C/path/to/your/buildspec.yml"

   This ensures that CodeBuild uses the specified buildspec file rather than looking for a default one.

3. If you're still experiencing issues, you can try running the codebuild_build.sh script directly instead of using the Docker run command. This script is part of the CodeBuild agent and can be more flexible. You would need to download and run it from your local machine:

   ./codebuild_build.sh -i <container-image> -a <output directory>

Remember to replace <container-image> with your CodeBuild image and <output directory> with your desired output location.

By following these steps, you should be able to see changes in your buildspec.yml reflected in subsequent builds when running CodeBuild locally on Windows using Docker.
Sources
Run builds locally with the AWS CodeBuild agent - AWS CodeBuild