Support CodeBuild local on Windows

[ssippe]

Hi,

Is it possible to run aws/codebuild/windows-base locally? I can't find any documentation on it.

I would be helpful to know what tools are installed on what paths to aid in creating a working buildspec.yml.

Cheers

[subinataws]

@ssippe - Unfortunately, no. CodeBuild local is only supported on Linux_x86 today. We also don't have the Windows Dockerfile available on this GitHub repo yet.

[ssippe]

It would be really helpful if I could just look at the dockerfile to figure out what resources are available. Can you show that?

…

On Wed., 25 Mar. 2020, 02:43 Subin Mathew, ***@***.***> wrote: @ssippe <https://github.com/ssippe> - Unfortunately, no. CodeBuild local is only supported on Linux_x86 today. We also don't have the Windows Dockerfile available on this GitHub repo yet. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#328 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAONHNJE6JYBOOWAEZYJTGLRJDPJVANCNFSM4LSFITDA> .

[ssippe]

I'm not sure I can use CodeBuild for building my .net framework application. If the following improvements were made, it would work fine.

Suggested Improvements:

• make the .net framework curated docker images are available
• make the .net framework curated docker files available so you could figure out how the environment is configured.
• Update the windows host version from the current 10.0.14393 so if you want to run your own docker image, you can the supported microsoft SDK containers. Anything that runs on 10.0.14393 is EOL.
• Make codebuild local is unavailable

Cheers

[adam-coster]

I would also love to have this feature.

[jyeagle]

Anything to make it easier to build legacy .Net Framework apps would be appreciated! I am trying to migrate some builds to AWS codebuild and it would help to know what is available in the windows images.

[finnairbadalov]

Need this as well

[joebarbere]

This would REALLY be a time saver. Having instructions on how to setup docker to access the registry where the CodeBuild images are hosted would be great (I assume its just in a private AWS ECR registry at the moment). As @ssippe mentioned, even then Dockerfile would be helpful to understand what is included in the image.

[richarddowner]

We would also benefit from having access to the windows code build image or Dockerfile, as we would like to extend the image to contain additional required build resources.

[matthewko-acl]

I also agree with this, having more insight into what's in the codebuild image or docker file would be good.

[denniswed]

any updates on windows support? i am having a heck of a time getting codebuild local work right on windows, even with GIT bash.

[AndreasLuckert]

Hello, have there been any advancements or plans on doing so soon?
My issue is also open since last fall.

[bestrus]

Something new for Windows @subinataws ? pls

[devt]

I have created a patch which fixes the issue for me using Git Bash. See PR #619 or my version

IMPORTANT NOTE: For the above to work, make sure your entire C: drive is mapped to Docker, so it shows up as /mnt/c/.

I actually use Rancher Desktop with the dockerd (mobi) container runtime (I think this is the default)
Example execution which works for me is below

mkdir -p "c:/tmp/lcb"
./codebuild_build.sh -i my-codebuild:latest -a /mnt/c/tmp/lcb -c -m -s $(pwd) -b buildspec/test.yml

The strange thing here is that bash (at least this version bundled with GitBash) mangles the paths and does not allow you to submit a path like /mnt/c/something. It somehow injects "C:/Program Files/Git/" at the beginning.

The workaround is to invoke PowerShell with the same params. PowerShell is kind enough not to mangle, like bash does.

IMPORTANT NOTE: For the above to work make sure to map the entire C: drive to Docker.

I actually use Rancher Desktop with the dockerd (mobi) container runtime. I think this is the default. My version of Rancher is 1.5.1

Note: The issue with path mangling should be fixed if you export MSYS_NO_PATHCONV=1