Fat Can, Docker and I look back on the quotes of First Gundam

Why is it swayed by Docker like this?

I participated in the day trip development training camp (Fat Can), which is held regularly at our company, for the first time in a long time. Recently, I've been busy with music activities (I like bad sideways), and it's been a while since I've been developing on holidays.

I struggled to build a Django environment using Docker, but with Dockerfile I was confused by the difference in docker-compose.yml, and I tried to force Pyenv into it. It's a disappointing result. It seems that he understands Docker, but in fact he understood it only shallowly. The final step is to build a Django environment directly in the EC2 environment while reflecting on myself.

Where is the guy who became full-fledged without being beaten! (Bright Noa)

From here, I will write something like my memorandum that I re-studied about Docker.

Docker container (container) ≠ Virtual Machine (VM)

Obviously, Docker has a different principle and idea from Virtual Machine, and The technology used is also very different. Compared to containers that share memory and storage as well as the kernel of the host OS Each VM is a separate (virtually) exclusive image. The container is a share house with shared kitchen, bath and toilet, and the VM is in one room of the apartment. The kitchen, bath, and toilet are like individual.

It's different from Zaku, what is Zaku! (Ramba Ral)

Container easily connects to another container

The network of both containers is the NameSpace and virtual of the Linux OS kernel. It can be realized by the function of NIC and virtual adapter (router). It is very flexible that the word virtual can be freely added / changed / deleted at the point. Bull and great. I misunderstood that communication between containers is a function of Docker (sweat).

Because I'm a little boy (Char Aznable)

Containers are easy to manage

It would be convenient to stop unnecessary containers and clone images from git to start necessary containers. Thanks to the NameSpace mentioned above, I am very grateful that it does not pollute other areas.

I've never been so happy (Amuro Ray)

This reflection

I ended up with a fat can who spent most of his time studying Docker.

I'm different from the one I used to be (Kai Shiden)

Next time, let's master Docker as we like and build a Django environment!

Acknowledgments

I learned a lot. -Introduction to Docker, the most understandable container in the world -Introduction to Docker

Recommended Posts

Fat Can, Docker and I look back on the quotes of First Gundam
[Docker] How to back up and restore the DB data of Rails application on docker-compose [MySQL]
I stumbled upon the development and publication of my first iPhone app
Looking back on the basics of Java
I tried using Docker for the first time
I compared the characteristics of Java and .NET
I installed Docker on EC2 and started it
I tried touching Docker for the first time
I touched on the new features of Java 15
I tried to summarize the state transition of docker
Docker the development environment of Ruby on Rails project
Verification of the relationship between Docker images and containers
I summarized the types and basics of Java exceptions
[WIP] I tried the configuration of Docker + Streama + NFS
[Personal memo] Looking back on what I got stuck in Docker ... including knowledge of Linux
I didn't understand the behavior of Java Scanner and .nextLine ().
I tried to summarize the basics of kotlin and java
Install docker and docker-compose on ubuntu in the shortest process
I tried JAX-RS and made a note of the procedure
I tried to build the environment of WSL2 + Docker + VSCode
I want to narrow down the display of docker ps
[Java] I thought about the merits and uses of "interface"
[Introduction] Installation of Docker Desktop for Mac for the first time and setup of virtual environment construction of CentOS