Posts

Digital Marketing

The integration between Docker and Amazon ECS

The integration between Docker and Amazon ECS allows developers to use the Docker Compose CLI to: Set up an AWS context in one Docker command, allowing you to switch from a local context to a cloud context and run applications quickly and easily Simplify multi-container application development on Amazon ECS using Compose files

Watching a file to keep the container running.

tail -f /dev/null

A container adds additional isolation not available when simply using chroot.

A container is extended version of chroot A chroot on Unix operating systems is an operation that changes the apparent root directory for the current running process and its children. A program that is run in such a modified environment cannot name files outside the designated directory tree. The term "chroot" may refer to the chroot(2) system call or the chroot(8) wrapper program. The modified environment is called a chroot jail.

Allow multiple Docker containers to communicate with each other by Docker network

For example a client application in another Docker container can access the database Server in the server container.  First, create a Docker network: docker network create goyun-info-net When you are creating and starting the server and the client containers, use the --network option to put them on network you created. For example: docker run --name=mysql1 --network=goyun-info-net -d mysql/mysql-server docker run --name=myapp1 --network=goyun-info-net -d myapp The myapp1 container can then connect to the mysql1 container with the mysql1 hostname and vice versa, as Docker automatically sets up a DNS for the given container names .  In the following example, we run the mysql client from inside the myapp1 container to connect to host mysql1 in its own container: docker exec -it myapp1 mysql --host=mysql1 --user=myuser --password For other networking techniques for containers, see the Docker container networking section in the Docker Documentation.

Fixed: AWS CodeCommit Permission Denied issue

When trying to push to the remote repo. Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. On your local machine, use a text editor to create a config file in the ~/.ssh directory, and then add the following lines to the file, where the value for User is the SSH key ID you copied earlier:   Host git-codecommit.*.amazonaws.com User APKAEIBAERJR2EXAMPLE IdentityFile ~/.ssh/ codecommit_rsa

Install Ajenti Control Panel on Ubuntu

systemctl: command not found on ubuntu docker

sudo apt-get install systemd Or re-install sudo apt-get install --reinstall systemd