AWS CodeBuild | AWS ECR | AWS CoudeBuild Push Docker Image to ECR | AWS CodeBuild Example

in this video I'm going to show you how to build docker images using AWS code build and push them to elastic container registry for this demonstration we need to have easier elastic container registry let's go ahead and create a new repository create that so we are going to use this repository to push all our docker images from code builder we need a sample project so in my github account I have one sample project which is node app you guys can take this as a reference when you guys do practice on it in this repository the most important file is build spec dot ml code Bill uses this Hamel file to decide how to build our application let me quickly walk you through this file so it easily has different phases like pre build build post build and the artifacts in sense when you start this build process before actually doing the build if you want to do something like I want to connect to ECR first then prepare certain details like which is my elastic container registry and commit hash I'm getting come in hash I'm using this commit hash to tag my docker image so image tag and so on so I am preparing certain things before I actually building my docker image then comes build phase so I have given list of commands that I want to execute to build my docker image couple of echo commands which says build started building docker image and this is the Walker command I want to use to build the image Daka build - T the repository URI this one and the version and so on then we are tagging it after the docker image is built first build we are pushing that image to our elastic container registry after code build if you want to deploy this image to elastic container registry I need to pass that information to the next phase those details I will be doing it in some other video but this video I want to focus only on how to take code from github build our image and push it to elastic container registry so these details as of now not very important so you can take this file as a reference and don't forget to change this repository URI let's copy this guy edit change here the rest remains good for me yeah commit the change we have easier we have a sample project using which we want to build our images if you want to practice you can import my project into your github account and practice at the next step is let's use code build the create build project I'm calling this node app description is optional let's leave all that information so I want to integrate my code build with github see for me I am already connected so that's why it's getting the information from my github account from my github account I want to select node app this you can leave so webhook this is optional when you select this whenever there is a push in github account github repository I want this code build to be triggered automatically for that we need to enable this check box and select the event for which you want triggers the environment so I want to build docker images probably need a environment where docker is installed correct so operating system ubuntu runtime standard so image you can choose any of this for this specific demo image version I am leaving it as default so this is very important you must select this check box otherwise you won't be able to execute docker commands inside code build service roll a code build might access elastic container registry it might access s3 even it might access some of the services for that a service role is required so I'm saying create new service role this automatically creates a service role if you have any existing customized service role then select this and choose that option there so bill spec this is what the input for code build the complete build process dip on this bill spec file that file is kept in node app project root directory so you don't have to fill these details if we are following default naming convention if file name is Bill spec dot ml and if this file is present in project root directory you don't have to mention that explicitly because by default it means the same for some reasons if you have a different file name and you're keeping it in a different location in such cases you have to explicitly provide that information so artifacts so where you want to upload all these artifacts in my case I don't want to upload upload artifacts to s3 I want to upload artifacts to my easier that information is configured already in Bill spec dot M L so I would say no artifacts here so logs if you have any issues with the build for troubleshooting all the stuff we need locks give some name for the law group it stores all your bill logs in that specific cloud watch group so randomly give some names there and create the build project if all goes good it should create your code build project ok I need to do one more change one more change so before doing that change let me show you the problem and accordingly let me change things so start build project we have only one project now you can set timeout if you want to set any timeout source we integrated with github and this is the repository start build it would take some time I will pass my video and I will be back once it is ready it has taken 1 2 minutes and if you see the status its failed you can troubleshoot that with help of the locks here see it's unable to log into elastic container registry the reason is we didn't set permissions go to I am so go and check your service role you're no dab service role see it ended couple of policies but there is no policy which grants access to easier so go to attach policies so Amazon easy to contain a registry full access in real time you have to customize this and keep it very restrictive to what your code build should get access to so attach policy after attaching that extra permissions you could say rebuild so again I want to pass my video for a while once the output is ready I will resume you it has built the image successfully and it's pushing that image to our elastic container registry or before that completes let's go too easy are the images successfully built and it is pushed to elastic container registry I would like to show one more so whenever I do changes to my github repository that should auto trigger how code build so right now we have couple of things right so this is the recent one when I do changes to my node app in github it has to trigger the next one let me open some file randomly do change and commit see that there is a new build in progress thanks for watching

Channel: Java Home Cloud

Views: 40,999

Keywords: java home, devops, java home cloud, devops tutorial, devops by javahome, devops by java home cloud, aws, aws tutorial, aws by javahome, aws codebuild tutorial, aws codebuild, aws codebuild github, aws codebuild docker, aws codebuild demo, aws codebuild ecr demo, aws codebuild ecr example, aws codebuild build docker image and push to ecr, aws codebuild javahome, aws codebuild example

Id: 3CcGtRidF9c

Length: 12min 3sec (723 seconds)

Published: Fri Jul 05 2019