Azure Pt. 3.1, Container image hosting…

Well, I paid a company to redo my resume. Not a lot of stuff out there at the moment by my current resume format seems a bit crowded and its probably good to have someone who deals with resumes day in and day out to take a look at it and figure out how to organize things and what to highlight. So much Linux experience with NAPA and im attempting to target a Windows Server Admin role but we will see how that goes haha. Anyway, back to Azure and realizing that this two test cert could take most of the year. This is fine with me. If I have extra time maybe ill start into the 70-744 but they are no longer offering that in January of next year and to be honest a Network+ and a Security+ with two MCSAs sounds better than a Core Infrastructure MCSE to me as its vendor diverse and implies the same thing with less confusion as to meaning. That’s not say that I don’t want the Core Infrastructure MCSE but I’m not sure I have the time/value for it unfortunately but it would feel awesome to pass the 70-744. It’s also becoming very apparent that cloud computing is the future so, here we are. Anyway, this is the part where I start throwing in questions and trying figure out what everything is.

One would assume that the data has to go into some type of storage for a container, assuming we are using Docker as that’s what I learned about on the 2016 MCSA but who knows. Lets take a look at how containers work in Azure. This make take a while or it may not. Who knows. Lets start with the link in the question: Deploy an Azure Web App Container

I dont know what YAML is, I’ve heard the term thrown around but I’m not super familiar with it so lets sort through that but you can see in the screen shot that its pointing to a container registry. Earlier they ran a command to pull your docker image from a github repo that has sample container images or you would assume its sample images but really its just code pointing to default docker test images, as seen below

Kind of confused by this as its running an update script and doesn’t seem to point to an image and appears to be updating an image which has a large potential to break any running apps you have on a container haha. Anyway, if your interested install docker on your machine and then download something like this: Couchbase and you’ve got a small VM running on your machine. Now lets figure out what YAML is

YAML (a recursive acronym for “YAML Ain’t Markup Language”) is a human-readable data-serialization language. It is commonly used for configuration files and in applications where data is being stored or transmitted. YAML targets many of the same communications applications as Extensible Markup Language (XML) but has a minimal syntax which intentionally differs from SGML .^[1] It uses both Python-style indentation to indicate nesting, and a more compact format that uses [] for lists and {} for maps^[1] making YAML 1.2 a superset of JSON.^[2]

Funny thing about programming languages, I’ve learned that every thing in 2020 is basically JAVA or XML haha. I’ve also found it very helpful to occassionaly poke around in Kali and walk through some basic stuff on Vuln hub as it promotes familiarity with Linux and unless you want to sit around and build web apps at home or something its sort of like Leapfrog learning. it Also comes with free super cool sunglasses and and a hoodie (follow @viss on twitter for more info haha)

Edit: now with hackerman HD images courtesy of Viss that I wasn’t sure where I had saved

Anyway, back to Docker on Azure. The point being this is dev ops and they have linked an article that is fairly specific and slightly confusing for infrastructure people with no background in containers. For the sake of “this is the article they linked” I’m going to start with Pipelines and then dig into the container process because the linked repo is concerning Azure Pipelines

There is a lot going on with Pipelines lol but this little graphic sums it up in common folk talk the best. As an added bonus be sure and note the underlying hackerman joke of ‘deploy to target.’ Also, have you read AWS documentation? Can you read technical documentation well haha, JFC! I think we have a little comedy club going for those … you know what. nevermind. its better this way. Ok, here we go Build An Image

This one makes sense, you throw in your docker file and this is a template that has images and isn’t just a piping code in. I don’t know, I could be fucking this up as I haven’t used docker super extensively but I sort of get the basics. All right, well its kind of clear on that one. Again, not really in devops so I would I have to do some more research and testing but I have found for learning this stuff ‘hacker man’ stuff is a great way to figure some things out. Again, I don’t recommend it for cool points, but local Defcon groups can be great fun . Anyway, Container Registry? (normally I don’t link the sale pages but I found this helpful)

Wow! Pipelines for patching! not..building images haha

And now we are back on Docker with the technical documentation Introduction to private Docker container registries in Azure (why not just use docker hub, pull your image over and pipe code to the container? Who knows … I’m not in sales or devops haha)

Azure Container Registry is a managed, private Docker registry service based on the open-source Docker Registry 2.0. Create and maintain Azure container registries to store and manage your private Docker container images and related artifacts.

Use Azure container registries with your existing container development and deployment pipelines, or use Azure Container Registry Tasks to build container images in Azure. Build on demand, or fully automate builds with triggers such as source code commits and base image updates.

All right, this is kind of what I was looking for Quickstart: Create a private container registry using the Azure portal

An Azure container registry is a private Docker registry in Azure where you can store and manage private Docker container images and related artifacts. In this quickstart, you create a container registry with the Azure portal. Then, use Docker commands to push a container image into the registry, and finally pull and run the image from your registry.

To log in to the registry to work with container images, this quickstart requires that you are running the Azure CLI (version 2.0.55 or later recommended). Run az --version to find the version. If you need to install or upgrade, see Install Azure CLI.

You must also have Docker installed locally. Docker provides packages that easily configure Docker on any Mac, Windows, or Linux system.

Alright, so you have to be running win10 pro to get docker because virtualization is locked on the home version and as such I cant run any hypervisor on my current main machine but I have two older machines that work fine for that and I use this for blogging and FL Studio mostly. I may upgrade at some point but jesus christ is it a pain in the ass to get a large SSD and windows 10 if you go through the dell site to order a PC. Not to mention! I would like to simply put in my volume license key that I bought off of eBay for a quarter of the price of what dell charges for windows 10 and have it mysteriously work so I can fuck with docker when I feel like it. Sorry for cussing. Back on track, it is looking like you may not be able to use public image repositories per the MSFT suggested method but I’m sure there are ways around that. Maybe? Regardless, now we know where docker images are hosted. Honestly, I think that’s a good place to stop for now as this turned into a wall of text fairly quick.