Blog post: describe how to build containers with GitLab Runner, AWS Fargate, and CodeBuild (July 31)

Proposal

Running containers in privileged mode is a known limitation of AWS Fargate. This means Docker-in-Docker (DinD), which enables the building and running of container images inside of containers, does not work on the AWS Fargate Custom Executor driver for GitLab Runner. The good news is that users are not blocked by this limitation and may leverage a cloud-native approach to build their containers as they consider a seamless integration to AWS CodeBuild in the CI/CD pipeline.

The way to autoscale GitLab CI on AWS Fargate is deeply covered in GitLab Runner's documentation. What we will describe in this blog post is how to instrument containers and the source repository to trigger AWS CodeBuild in order to build container images.

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)