archive/theorangeone.net-legacy
1
Fork 0
Code Activity

Add docker tag

Browse source
This commit is contained in:
Jake Howard 2022-01-01 11:32:52 +00:00
parent 1bd9b5c971
commit 086df489c9
Signed by: jake
GPG key ID: 57AFB45680EDD477
9 changed files with 17 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/posts/backup-restore-containers.md → content/posts/backup-restore-docker-containers.md
View file

@ -1,8 +1,10 @@
--- ---
title: Backing up and restoring containers title: Backing up and restoring Docker containers
date: 2020-12-06 date: 2020-12-06
image: unsplash:CpsTAUPoScw image: unsplash:CpsTAUPoScw
tags: [containers, linux, self-hosting] tags: [containers, linux, self-hosting, docker]
aliases:
- /posts/backup-restore-containers/
--- ---
You should back up your data, properly! If you're not, you're playing a dangerous game with fate. Computers are pretty reliable, but they also go wrong, often. You should always backup your files, but backing up a containerized application isn't quite as simple. You should back up your data, properly! If you're not, you're playing a dangerous game with fate. Computers are pretty reliable, but they also go wrong, often. You should always backup your files, but backing up a containerized application isn't quite as simple.

2
content/posts/containers-as-root.md
View file

@ -2,7 +2,7 @@
title: Container processes shouldn't run as root! title: Container processes shouldn't run as root!
subtitle: \"What's wrong with containers running as root?\" subtitle: \"What's wrong with containers running as root?\"
date: 2020-08-18 date: 2020-08-18
tags: [self-hosting, security, containers] tags: [self-hosting, security, containers, docker]
image: https://www.threatstack.com/wp-content/uploads/2017/06/docker-cloud-twitter-card.png image: https://www.threatstack.com/wp-content/uploads/2017/06/docker-cloud-twitter-card.png
--- ---

2
content/posts/docker-in-lxc.md
View file

@ -3,7 +3,7 @@ title: Docker in LXC
subtitle: A hack or a haven? subtitle: A hack or a haven?
date: 2021-09-30 date: 2021-09-30
image: unsplash:uyDNkvdIKv8 image: unsplash:uyDNkvdIKv8
tags: [linux, containers, server-2020, self-hosting] tags: [linux, containers, server-2020, self-hosting, docker]
--- ---
Docker is a great containerization technology for running applications. It keeps multiple applications completely isolated from each other, only allowing connections exactly when you tell them to. But what if you're on a hypervisor? You want your host OS to be as lean as possible (else it defeats the point), but you don't want the overhead and additional complexities which come from full on VMs? Docker is a great containerization technology for running applications. It keeps multiple applications completely isolated from each other, only allowing connections exactly when you tell them to. But what if you're on a hypervisor? You want your host OS to be as lean as possible (else it defeats the point), but you don't want the overhead and additional complexities which come from full on VMs?

2
content/posts/docker-lxc-storage.md
View file

@ -2,7 +2,7 @@
title: Reducing storage usage for Docker in LXC title: Reducing storage usage for Docker in LXC
date: 2021-10-01 date: 2021-10-01
image: unsplash:FJTz_ASf_BI image: unsplash:FJTz_ASf_BI
tags: [linux, containers, server-2020, self-hosting] tags: [linux, containers, server-2020, self-hosting, docker]
--- ---
Docker containers (like [onions](https://www.youtube.com/watch?v=GZpcwKEIRCI)) have [layers](https://docs.docker.com/storage/storagedriver/). In your `Dockerfile`, each new `RUN`, `COPY` or `ADD` line creates a new layer (so do the others, but not ones which affect the filesystem). Each layer contains only the files which changed from the previous layer, which allows layers to be shared between containers, reducing download size and disk usage. It's possible to access individual layers though, so don't go adding extra layers to delete secrets in a futile attempt at security. Docker containers (like [onions](https://www.youtube.com/watch?v=GZpcwKEIRCI)) have [layers](https://docs.docker.com/storage/storagedriver/). In your `Dockerfile`, each new `RUN`, `COPY` or `ADD` line creates a new layer (so do the others, but not ones which affect the filesystem). Each layer contains only the files which changed from the previous layer, which allows layers to be shared between containers, reducing download size and disk usage. It's possible to access individual layers though, so don't go adding extra layers to delete secrets in a futile attempt at security.

2
content/posts/increase-docker-ip-space.md
View file

@ -3,7 +3,7 @@ title: Increase your Docker IP space
date: 2020-10-30 date: 2020-10-30
image: unsplash:fN603qcEA7g image: unsplash:fN603qcEA7g
subtitle: Fixing "could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network" subtitle: Fixing "could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network"
tags: [containers, self-hosting, linux] tags: [containers, self-hosting, linux, docker]
--- ---
Recently, I started setting up a new application on my docker host. It was late in the day, and I just wanted to get something up and working to play around with. Just my luck, I was met with wonderfully cryptic error: Recently, I started setting up a new application on my docker host. It was late in the day, and I just wanted to get something up and working to play around with. Just my luck, I was met with wonderfully cryptic error:

2
content/posts/keeping-docker-containers-updated.md
View file

@ -2,7 +2,7 @@
title: Keeping your Docker containers up to date title: Keeping your Docker containers up to date
subtitle: Updating your applications with minimal effort subtitle: Updating your applications with minimal effort
date: 2020-07-27 date: 2020-07-27
tags: [self-hosting, containers] tags: [self-hosting, containers, docker]
--- ---
Last year, I switched all of my hosting from arbitrarily installed packages to Docker. This made installing and configuring incredibly simple, but updating a little less defined. Whilst Docker itself is updated through the system package manager (probably), the containers themselves aren't. Last year, I switched all of my hosting from arbitrarily installed packages to Docker. This made installing and configuring incredibly simple, but updating a little less defined. Whilst Docker itself is updated through the system package manager (probably), the containers themselves aren't.

4
content/posts/upgrading-docker-databases.md
View file

@ -1,6 +1,6 @@
--- ---
title: Upgrading Databases in Docker title: Upgrading Databases in Docker
tags: [containers] tags: [containers, docker]
date: 2021-12-23 date: 2021-12-23
image: unsplash:lRoX0shwjUQ image: unsplash:lRoX0shwjUQ
--- ---
@ -9,7 +9,7 @@ For me, every Monday is updates day. I run through all the entries in my Ansible
Database upgrades are _fun_ at the best of times. By their nature they contain some of the most important data to an application's operations. When you add Docker into the mix, it can get even more complex. But it doesn't have to be difficult. With a little planning, and a tiny amount of downtime, the upgrade process is just a few simple steps, depending on the engine you're using. Database upgrades are _fun_ at the best of times. By their nature they contain some of the most important data to an application's operations. When you add Docker into the mix, it can get even more complex. But it doesn't have to be difficult. With a little planning, and a tiny amount of downtime, the upgrade process is just a few simple steps, depending on the engine you're using.
Before you do any of this, absolutely make sure you have backups. Containers are wonderfully [simple]({{<relref "backup-restore-containers">}}) to back up, and you do not want your upgrade to result in complete loss of data! I give each application its own database container, to keep things separate and clean, but these upgrade instructions are the same regardless. Before you do any of this, absolutely make sure you have backups. Containers are wonderfully [simple]({{<relref "backup-restore-docker-containers">}}) to back up, and you do not want your upgrade to result in complete loss of data! I give each application its own database container, to keep things separate and clean, but these upgrade instructions are the same regardless.
## PostgreSQL ## PostgreSQL

1
content/projects/docker-website-server.md
View file

@ -2,6 +2,7 @@
title: Docker Website Server title: Docker Website Server
repo: RealOrangeOne/docker-website-server repo: RealOrangeOne/docker-website-server
subtitle: Static file server designed for serving websites subtitle: Static file server designed for serving websites
tags: [docker]
--- ---
If you, like me, have a website, you'll probably need some way of serving it. And if, like me, your website is static, `nginx` is a great, lightweight and insanely fast file server. But, how do you configure it? Sometimes, you just don't care, and want someone else to do it for you - like me! If you, like me, have a website, you'll probably need some way of serving it. And if, like me, your website is static, `nginx` is a great, lightweight and insanely fast file server. But, how do you configure it? Sometimes, you just don't care, and want someone else to do it for you - like me!

5
content/tags/docker/_index.md Normal file
View file

@ -0,0 +1,5 @@
---
title: Docker
---
[:whale:](https://www.docker.com/).