Тёмный

Fix Docker Issues 

Scotti-BYTE Enterprise Consulting Services
Подписаться 5 тыс.
Просмотров 278
50% 1

This tutorial addresses issues with Docker and how nesting docker applications inside of Incus/LXD containers is a best practice. I introduce a couple of helpful utilities along the way.
Show Notes:
discussion.sco...
------------
Come visit us at: www.scottibyte...
Discourse: : discussion.sco...
RocketChat: chat.scottibyt...

Опубликовано:

 

1 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 7   
@ewenchan1239
@ewenchan1239 6 месяцев назад
Great video! Three things: 1) I was reading somewhere that when you "update" or "upgrade" a Docker application, it doesn't actually update/upgrade it. What it actually does, in the background is that it destroys the Docker container with the application running in it, and then re-creates it. I also remember reading, a little while back now, that this is the reason why persistent volume/data storage should be used so that when you do this "destroy/re-create to upgrade/update", it won't delete your data (if you keep it on persistent storage). 2) I've been playing around with using Portainer to help do some of the Docker application management (rather than using the CLI) as it is more likely for me to make a mistake with the CLI than I am with the GUI. This works if I am not trying to pass a GPU through to a Docker container via Portainer. If I am trying to pass a GPU through to a Docker container, right now, I am still running those applications in their own LXC container. (For now.) 3) In regards to the point re: single docker server running multiple applications -- can't you resolve some of those issues by running multiple docker servers that are just HA clones of each other docker server? Or is that more of a Kubernetes thing (with Docker clusters)?
@scottibyte
@scottibyte 6 месяцев назад
When you stop a docker application with "docker compose down" it does not delete the container. If you follow with a "docker compose pull" you will get a new image if there is one. When you do another "docker compose up" the old containers are still on the system. A valid warning is that some applications leverage this and reuse a container in subsequent runs that is "down" but not "deleted". Rocketchat is one such app. When a container is "downed" it is not necessarily destroyed and the image to create it is still existent as well. There are actually many scenarios where dangling vfs components end up hanging around forever. One key one are system and container shutdowns are not always "clean" and docker simply doesn't know how to clean up after itself. Portainer, like other GUI's is a nice tool for monitoring. Portainer is a "black box". It's easy to make mistakes in a GUI by accidentally "wholesaling" a command that affects an entire data structure. I emphasize the CLI because 1) you learn to understand what you really doing and 2) it helps teach the infrastructure. GUI's are nice, but they are a crutch. I run a single docker application in an Incus/LXD container because 1) I don't want to have to juggle port numbers and 2) I don't want a docker problem to "down" several applications at once. Yes, the alternative would be Kubernetes. I don't use Kubernetes because it is just too convoluted to provide proper accesses to apps with databases IMHO. By the way, chat on chat.scottibyte.com/.
@MrDevonscott
@MrDevonscott 6 месяцев назад
As always, very helpful, Scott! 😀
@scottibyte
@scottibyte 6 месяцев назад
Thanks!
@try-that
@try-that 6 месяцев назад
I use OMV 7. I watch all videos, but I still prefer OMV. My main reason is the time it takes to update my approx 30 containers. Now OMV has a excellent docker compose plugin that can do a shed load of stuff (I didn't know about the var dirt, so going to look into that and might suggest the author looks this video up) It can do lxc, not sure if it will change to incus, I'll have to check. It can also do vms and just added a kubernetes plugin but I digress. But if I use a lxc for each docker that a lot of updating, once I've done apt update etc, and then the containers. But I'm willing to have my mind changed, but at the moment OMV 7, does everything and more for me at the moment.
@scottibyte
@scottibyte 6 месяцев назад
I understand folks that use apps like OMV and Proxmox. However, my focus is on teaching folks how to use and understand the actual infrastructure. Applications like OMV provide an easy and encapsulated way to launch and maintain applications. The problem is when it breaks, the internals are not always very transparent. I advocate for simplicity and also for applications that provide a more basic approach. For that reason, I am trying to bring technologies like LXD and Incus to the limelight because they have less press than OMV and Proxmox and others.
@try-that
@try-that 6 месяцев назад
I get it, that's why I watch your stuff, because I do like to understand the more low level stuff. I could do Debian on bare metal and probably have a very like for like system to my OMV, but as you say, I like OMV as it's is easier for NFS shares etc. I'd probably still use docker and use Dockge to manage them. I've looked at cockpit, but the disk space OMV takes up it less than 10gig. I look forward to more videos 😁
Далее
Incus Docker Containers
38:10
Просмотров 617
Лайфак года 😂
00:12
Просмотров 103 тыс.
Docker in Incus with Incus Volumes
25:22
Просмотров 374
Incus Containers Step by Step
31:44
Просмотров 3,6 тыс.
Docker vs Virtual Machines (why you NEED both)
18:24
Просмотров 14 тыс.
Docker Compose Pitfalls
12:46
Просмотров 275
Docker Networking Crash Course
49:19
Просмотров 82 тыс.
18 Weird and Wonderful ways I use Docker
26:18
Просмотров 207 тыс.
Virtual Machine (VM) vs Docker
8:52
Просмотров 205 тыс.