‫All right.
‫So first up.
‫Is there a way to build and run containers from get Mono repo.
‫I mean multiple containers I am writing multiple services and go in and do that in a mongo mono repo.
‫And now it's time to incorporate some automation.
‫Yeah absolutely.
‫And I think that you have other people there also answering your questions Alexandra.
‫Yes definitely.
‫You can do that.
‫You basically could just clone a repo down move to the directory where you want that Docker file and
‫then do a docker build your Docker files don't have to be called Docker file the default name that Docker
‫will use when you do a docker build is looking for a file called Docker file.
‫But you can call it you know container file you can tell it whatever you want container build.
‫You know you can make your own standard.
‫And then when you do a docker build you're going to specify a dash F to find the file that you wanted
‫to call.
‫This is also true of Docker compose if Docker compose has a default file name.
‫But you can always use dash F to specify whatever file you want.
‫And with Docker files remember the thing about Docker files is the con the the directory that you're
‫in for the context which is that last little thing that you do in a doc or build command.
‫For instance if you do a c it's just zoom in
‫if you do a docker build and look at the help
‫the last little thing there is the path.
‫So ideally you whatever the path is or the context for where you're building it that's where the docker
‫file will start doing its work from.
‫And so sometimes I get a question where people say I want to include files in my Docker image that are
‫in a completely different path like up my directory chain and that's not something that Docker Build
‫does because when you specify that path or location for where you're going to start building Docker
‫will you see if you see at the beginning of a docker build it will take all the files in that directory
‫and all sub directories and put them into a tar ball and then push them to the doctor engine wherever
‫that is if that might be your local machine that might be a server that's remote.
‫And so if there's a file you're trying to copy in from somewhere else it's never going to get that file.
‫So make sure that when you're doing this that you're always building that context from the directory
‫you want like if you're go apps or in their own sub directories that's fine.
‫Just do a docker build specify the file name and it specify that directory as the build path at the
‫end there and you'll be good.
‫Good question.