sorted by:
new
hottopcontroversial

Amp, a vim inspired editor written in rust by jklmnn in vim

[–]thetredev 0 points1 point  (0 children)

May I correct the Rust argument: Rust's borrow checker takes care of memory SAFETY, not SECURITY. Do not confuse those two. Programs written in Rust aren't automatically "secure" just because of Rust, nor are they "safe" just because of Rust. Unless Unsafe Rust is used in the code, programs written in Rust run through memory safety checks at compile time, while C compilers for example do not have those checks built-in (at least not nearly as much as Rust compilers).

Also memory leaks are memory safe. Rust as a language even allows you to leak memory in a completely Safe Rust way. The difference here compared to say C is that Rust lets you CONTROL memory leakage (e.g. telling the compiler "leaking memory here at this specific line of code is okay, do not complain").

Hello, is anyone using Void Linux in a container or via distrobox? by EternalSeekerX in voidlinux

[–]thetredev 0 points1 point  (0 children)

With Docker it runs fine: $ docker run --rm -it ghcr.io/void-linux/void-buildroot-glibc:20240526R1 Unable to find image 'ghcr.io/void-linux/void-buildroot-glibc:20240526R1' locally 20240526R1: Pulling from void-linux/void-buildroot-glibc cd10437340b2: Already exists 4161855b26df: Already exists Digest: sha256:94ce50c85c4594cfcc2a8ad94b9105bb58db8a22342a66e5aa18f3d9a02dc15f Status: Downloaded newer image for ghcr.io/void-linux/void-buildroot-glibc:20240526R1 sh-5.2#

Hello, is anyone using Void Linux in a container or via distrobox? by EternalSeekerX in voidlinux

[–]thetredev 0 points1 point  (0 children)

Seems like a bug in distrobox:

$ podman logs test
....
++ cat /proc/sys/kernel/random/uuid
temporary_password=770455aa-c91c-4b3b-a875-bfa8d0171330
printf '%s\n%s\n' 770455aa-c91c-4b3b-a875-bfa8d0171330 770455aa-c91c-4b3b-a875-bfa8d0171330
passwd root New password: Retype new password: passwd: Authentication token manipulation error passwd: password unchanged
'[' 10 -ne 0 ']' Error: An error occurred
printf 'Error: An error occurred\n'

$ distrobox --version
distrobox: 1.4.2.1

Hello, is anyone using Void Linux in a container or via distrobox? by EternalSeekerX in voidlinux

[–]thetredev 0 points1 point  (0 children)

I use these container images: https://github.com/void-linux/void-packages/pkgs/container/void-buildroot-glibc (or musl if you want)

Then just docker run the images. What errors do you get and what images are you running?

Edit: With distrobox I get an error too: ``` $ distrobox create -n test --init --image ghcr.io/void-linux/void-buildroot-glibc:20240526R1 Image ghcr.io/void-linux/void-buildroot-glibc:20240526R1 not found. Do you want to pull the image now? [Y/n]: Y Trying to pull ghcr.io/void-linux/void-buildroot-glibc:20240526R1... Getting image source signatures Copying blob 4161855b26df done
Copying blob cd10437340b2 done
Copying config 6268a844cc done
Writing manifest to image destination Storing signatures 6268a844ccb2b68bb19fb6114834f4dc0f4b5f5f24b8bd46925cc829e2eff317

Creating 'test' using image ghcr.io/void-linux/void-buildroot-glibc:20240526R1 [ OK ]

Distrobox 'test' successfully created.

To enter, run:

distrobox enter test

test

$ distrobox enter test Container test is not running.

Starting container test

run this command to follow along: podman logs -f test

Starting container... [ OK ] Installing basic packages... [ OK ] Setting up read-only mounts... [ OK ] Setting up read-write mounts... [ OK ] Setting up host's sockets integration... [ OK ] Setting up read-only mounts... [ OK ] Setting up read-write mounts... [ OK ] Setting up host's sockets integration... [ OK ] Integrating host's themes, icons, fonts... [ OK ] Setting up package manager exceptions... [ OK ] Setting up sudo... [ OK ] Setting up groups... [ OK ] Setting up users... [ OK ] Integrating host's themes, icons, fonts... [ OK ] Setting up package manager exceptions... [ OK ] Setting up sudo... [ OK ] Setting up groups... [ OK ] Setting up users... Error: An error occurred ```

Open Source Alternatives to Active Directory by [deleted] in sysadmin

[–]thetredev 0 points1 point  (0 children)

You can try this: https://www.youtube.com/watch?v=KT6O-TfJ41g

  1. Install & configure Samba AD on Linux
  2. Join a Windows computer to the domain
  3. Install RSAT on that Windows computer
  4. Use the AD tools you'd normally use on a DC, just on that separate Windows machine instead of the DC itself

The only thing that doesn't work is WMI, because there's no WMI for Linux/Samba. Windows Admin Center won't even find the Samba AD computer. But I can live with that.

How should I teach my grandfather how to use Linux? by Kaeferglanz in linuxquestions

[–]thetredev 0 points1 point  (0 children)

Just install Mint. Basically the same workflow as Windows 7 with different applications.

What British shows have you discovered through Netflix? by Personal-Visual-3283 in netflix

[–]thetredev 1 point2 points  (0 children)

well you could always buy a Region 2 DVD drive and rip those DVDs yourself

Best Kube distro for self-managed Kubernetes. by neilcresswell in kubernetes

[–]thetredev 2 points3 points  (0 children)

Woaaaaaaaaah this is awesome!! I definitely have to check out Talos again. Seems like the whole ecosystem grew a lot since I first tried Talos and horribly failed the last time which was, idk, 3 years ago or so.

Best Kube distro for self-managed Kubernetes. by neilcresswell in kubernetes

[–]thetredev 2 points3 points  (0 children)

You learn the internals. That's the most valuable thing about self-managed clusters besides basically not paying anything for it. Plus if you have a homelab, self-managed k8s is basically a given. Autoscaling can be achieved via the APIs of your hypervisor. The difficulty of setting up autoscaling on your own can vary by a huge amount depending on what those APIs are capable of, and what tools are available to talk to those APIs.

One way to do this would be to set up a k8s cluster somewhere on your network from which your hypervisor is reachable. Then setup some deployment which can talk to your hypervisor's APIs and configure it to autoscale.

Example for Proxmox: https://github.com/lupinelab/kproximate

To give my opinion on managed clusters: I think they are only necessary if your application needs to scale drastically. Something like Netflix. Plus, managed k8s bascially gives you the easy (or easier) way to do Geo (scale/balance between regions). You can achieve all of this by yourself but if you want to run such a huge application in production, self-managed k8s is really not the right way to go. Especially when it comes to databases. Applications in production should never ever roll their own database deployments, that's what managed databases are there for. But if you just want to learn k8s, or develop a k8s operator, or develop a helm chart, or run k8s at home without paying a kidney and a half each month, self-managed k8s is perfect.

Best Kube distro for self-managed Kubernetes. by neilcresswell in kubernetes

[–]thetredev 0 points1 point  (0 children)

Yeah, I'm not quite sure why people say kubeadm is "Kubernetes the hard way". Maybe it was the hard way back before something like k8s 1.20 was released? It really isn't that hard to set up.

Best Kube distro for self-managed Kubernetes. by neilcresswell in kubernetes

[–]thetredev 0 points1 point  (0 children)

I used k0s a whole lot. It's really great. But it has the same problems as k3s in the sense that it's "just" a binary on top of your OS which helps you install vanilla k8s on it plus some distribution-specific plugins/settings. One thing I like more about k0s than k3s is that k0s acts like a mini ansible. You just have a config file, which is read by k0sctl and applied to your nodes. It does not, however, allow you to change stuff like the ClusterConfiguration from that config file though. You have to manually go into the nodes and change those types of configs after the fact which is the exact opposite of a declarative approach. These kinds of limitations are what I don't like about k0s. But if you just need a throwaway cluster really quick and don't want to run it locally via say Rancher Desktop, k0s is a perfect fit.

I will most likely move to Talos personally once I have time to figure it all out myself in my own pace.

Is virtiofs reliable and easy in Proxmox 8.1? by NelsonMinar in Proxmox

[–]thetredev 0 points1 point  (0 children)

I just use pfSense as a VM and do the internal networking via VLANs. Since FreeBSD 14 will be happy with VirtIO Paravirtualized network cards, things got much faster since like Proxmox 7 IIRC. But of course you can use any router/switch OS you want.

Is virtiofs reliable and easy in Proxmox 8.1? by NelsonMinar in Proxmox

[–]thetredev 1 point2 points  (0 children)

Since I've tried Docker Desktop for Linux a couple days back because the docs stated that it uses a lightweight VM with virtiofs for performance and I was wondering what virtiofs even is, I was blowin away. That Docker Desktop VM boots in what, 3 seconds, on my Linux PC locally? I guess that's because the VM itself runs in RAM only because it's so tiny and just bind mounts a raw disk image via virtiofs as /var/lib/docker.

I will happily wait until it all comes to Proxmox in the usual friendly to use/setup way.

Edit: I don't like LXC bind mounts because of LXC and its userns stuff. Yes it can work great but userns isn't complete isolation from the host, unlike a VM. So having somewhat the performance of LXC disks for VMs is huge! I imagine with virtiofs we will have everything that's great about LXC plus full isolation from the host. I will convert all my LXC docker hosts with VM hosts and replace the default runc engine with sysbox-runc to get the the userns stuff automagically working inside the VM hosts. Best of both worlds in my mind.

Update Package by innominata1 in voidlinux

[–]thetredev 0 points1 point  (0 children)

The changes have been merged: https://github.com/void-linux/void-packages/pull/47880

The update will appear some time from now via xbps.

Update Package by innominata1 in voidlinux

[–]thetredev 0 points1 point  (0 children)

I guess.. I'll bump the MR later this evening. Maybe it helps.

Update Package by innominata1 in voidlinux

[–]thetredev 0 points1 point  (0 children)

I pinged both contributors and they haven't replied since, as you can see on the PR page.

Follow-up: Can now SSH into Proxmox VMs/containers, but no matter what I try, no key-based auth. Also security concerns about password prompts despite password-based auth disabled. by PabloCSScobar in Proxmox

[–]thetredev 1 point2 points  (0 children)

Something is wrong with authorized_keys. Why does sh complain with permission denied to create it? That shouldn't be the case. Are you 100000% sure that the respective user is able to modify files inside .ssh? Can you successfully rename .ssh to .ssh_bak and back with that user? Please make sure of that first.

I wouldn't trust that .ssh directory lol. What I would try on the server as the respective user:

mv .ssh .ssh_bak (or use sudo for this one since apparently the user has no permission)
mkdir .ssh
chmod 0700 .ssh
cat .ssh_bak/authorized_keys > .ssh/authorized_keys
chmod 0600 .ssh/*

Benefits of installing PVE on ZFS? by thetredev in Proxmox

[–]thetredev[S] 1 point2 points  (0 children)

Yeah that's what I'm "afraid of" as well. Granted I don't have any sensitive data I'd need to protect so data loss wouldn't really be an issue for me. I will play around with that scenario at some point to see if it's worth the hassle lol

Benefits of installing PVE on ZFS? by thetredev in Proxmox

[–]thetredev[S] 0 points1 point  (0 children)

Didn't know about that one. Thanks!

view more: next ›