Sender | Message | Time |
---|---|---|
25 May 2023 | ||
but at some point in the future hopefully i can replace most of that with 3 VMs with my k3s nodes :P | 13:21:52 | |
but my kubernetes knowledge is not good enough to migrate | 13:22:12 | |
there is also probably much more to say about this topic. this was just a small overview and stuff to think about | 13:23:30 | |
In reply to @james:jameskitt616.oneOne VM does not limit you to a single IP. Are you saying storage is hard for the base VM or the docker containers? For me these are separate things. | 13:44:30 | |
In reply to@chancem:mooreltd.net
well true, you can assign as many IPs to a vm as you want. i meant to say, you can only use e.g. port 80 once on that machine, so you gotta rebind all your services web ui's, different databased or whatever to different ports | 13:47:00 | |
for the base VM, e.g. you create a VM with 10 gb storage, but it's not enough. you got extra work expanding it. | 13:48:09 | |
if it's an issue for you or not is i a different story | 13:48:21 | |
In reply to@chancem:mooreltd.netofc storage and ip assignment are different things. never said sth else | 13:48:52 | |
In reply to @james:jameskitt616.oneRight I meant storage for the Containers is separate from the host VM. Not storage vs IP. | 13:50:45 | |
ah | 13:50:52 | |
the storage point also depends on your setup, if u got some centralized place e.g. network storage, it doesnt matter as much | 13:52:26 | |
In reply to @james:jameskitt616.oneTrue, I prefer to not expose the containers directly but through a reverse proxy. Sorry not trying to be contrariwise just trying to help further discussion in the hope of helping out the original poster. | 13:55:17 | |
In reply to @rails11326206827:matrix.orgI'm just running on bare metal, but using different network namespaces for different containers (some go to the generic services VLAN, some in IoT vlan...) | 13:59:07 | |
Thanks for the insight guys! Maybe I'll look into separating my "exposed" apps like gitea and jellyfin,emby to a their own LXC or VM as if they got hacked I don't want them to spread. | 14:35:40 | |
I was also thinking of using a SSD drive just as a storage drive for the docker containers data. In theory, I could make snapshots and backup that SSD easier than backing up a whole VM's disk each time | 14:36:58 | |
if you don't put the exposed apps into their own networking namespace it doesn't matter if they are lxc or vm or containers in general, then they will be able to contact other parts of your network. I've divided my network into a bunch of small VLANs with strict firewall rules for forwarding between them, but also have the lazy vlan for my generic services which aren't exposed outside of my lan | 14:43:09 | |
19:44:03 | ||
27 May 2023 | ||
14:21:58 | ||
29 May 2023 | ||
13:54:59 | ||
30 May 2023 | ||
07:07:23 | ||
12:19:04 | ||
31 May 2023 | ||
08:25:31 | ||
11:54:15 | ||
19:10:05 | ||
So I have share point/one drive storage to backup. Any chance anyone knows of a Linux tool thst allow to upload backup files using a Microsoft storage solution | 23:30:02 | |
1 Jun 2023 | ||
rclone or duplicity maybe | 00:19:12 | |
Yep. Rcone or Rsync | 00:19:35 | |
Nevermind, it gives more errors than desirable. | 01:14:09 | |
07:08:17 | ||
07:34:39 |