Getting Started with Containers

For a while now, I’ve been wanting to know and learn more about containers. Nothing like a new job that specializes in containers to jump start that process.

If anyone is wondering where a good starting point is for learning what containers are, might I recommend the Docker tutorial container getting-started.

$ docker run -d -p 80:80 docker/getting-started

This is a simple image that includes a tutorial website that takes you through the basics of using Docker. Goes through how to pull an image, build an image with code, update an image, and deploy all with using the CLI. Doesn’t really get into orchestration but does bring it up near the end. However, an added benefit in my book, it’s a fully functioning image that includes a multi-page website. Perfect for running quick container tests.

It may not be what you intend to do with a container, but it is very nice baseline. So much so, I’ve started using it to play around with the container services in AWS. Started off by deploying a copy of it to an ECR repo. From there, I’ve used it to test out different scenarios in ECS and EKS. Testing out EC2 vs Fargate instance types; testing out multiple deployments behind a load balancer; and testing a multi-container task. Perfect for helping me know I’m deploying my containers correctly and they work. I know I can build my own container and test it locally, but I haven’t gotten to that point yet.

I do have a couple of my own ideas to try testing out as well. Just need to build the images. Current plans include my Discord bot, a V Rising game server, and some of my own website builds. The bot will be interesting as I haven’t yet tested .NET Core in Linux and want to give that a try. The V Rising server is Windows only, so that will be nice experience with a Windows container. The websites will likely be Blazor/.NET Core, so Windows is a given; but Linux is an unknown. Similar to my Discord bot currently. Either way, I’ll be learning along the way.

Azure Update

Okay, so I started an Azure account, created a Web app project tied to Azure Dev Ops, and I just finished deleting the project.  While I admit, I haven’t had the time to really dedicate to it; but the decision game to cost. Should have done better research. I have the free credit, but at the rate I was burning through it, it wouldn’t have lasted long.

Going to count my loses and regroup once I can better understand the cost being each service. I still have a fair amount of my credit left so it isn’t so bad. Just need to make sure I have time to delve deeper. For now, AWS.

Microsoft Azure, Why Not!

While still struggling to find my groove in re-balancing my life, I’ve decided to expand my Cloud computing by setting up a Microsoft Azure account. Figured since I’m already using Azure DevOps to track my project, why not dig deeper.

So not only did I setup my account, I went all out by creating a web application server tied directly into Azure DevOps with a full pipeline to manage it. Git, Build, and Deploy all covered. CI/CD here I come. While I’m familiar with this at work and essentially helping to migrate a project over into a CI/CD structure, I’ve yet to play with a full pipeline enabled application.

Now I just need to be careful not to overload myself with to many projects. While by the time I finish with work, and now having to handle another college class, I can’t say I’m all that gun ho to work on more projects. Fortunately, I honestly find enjoyment in playing around with new technology. Just need to re-balance myself.

Blog Migrated to AWS!

Alright, will have to see how this goes. Migrated my WordPress blog onto my own server in AWS. The migration wasn’t a completely smooth as the template isn’t 100% the same. Will definitely be tweaking my custom CSS to get everything right; but this is why I did it. Best way for me to learn is to start playing around with things. Just hope this doesn’t all blow up on me somehow. I’ll keep my page up as a backup; but will start pointing everyone here.