Skip to main content

Docker: The Whale's Stuck


Docker 1.2 - Words Mean Things

Images - The blueprints, make up the basis of containers. [docker pull to get Busybox]
Containers - Made from images to run the application [docker run of Busybox image]
Daemon - Background service managing running, building, distributing docker containers
Client - The Command Line that talks to the daemon, though it can be a GUI. I prefer cmd line.
Hub - Registry - Directory - of images.

2.0 - How to Run A Static Website

  1. Pull image from Hub
  2. Run Container
  3. See how to run a webserver
Well, mission (sort of) accomplished!



Use a site already hosted on a registry for this demon.

Locally, it’s not here. So we have to get it from the registry and run it.

Nginx is running… - That’s good!



But there are more commands we have to put in - and as you can see, my prompt (Morganwarss-MacBook-Air:~ morganwars$) is gone.

Yet, somehow…

It works? And my Wifi is off, so it really is using a local port.




Well, let’s make our own Image. Remember how we did it with Busybox?

We can pull specific versions of images, if you don’t provide specifics, Docker will get the latest version - and you may not want that.

And images go even further than that!

Base Image - No parent images, usually with an OS.
Child Images - Build upon base images, add additional functionality.

Official images - Supported by the people at Docker, usually one word (or phrase) long.

User images - Made by us! Formatted by user/image-name

I’m still iffy on how to move about containers.

Anyway, we clone the prakhar1989/docker-curriculum repository and change directory to one about a flask-app. This application is written in Python.

the onbuild version of things does the boring stuff to get an app running.

And the python:3-onbuild app isn’t found, so I think we’re going back to the drawing board with this demo.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl