Search results

Well, while for sure integrity of the File is important, if a few links here and there are broken, I don't see that as a valid Reason to abort everything and delete the 99.9% good Container. I already faced an Issue where the Fedora OCI Image didn't have the CAPs set correctly, so I had to...

Which Template did you use ? Maybe I tested the only 2 that had an Issue :p .

Anything weird I am doing ? I seem to hit Edge Cases all them Time. It seemed to me like a pretty standard Container Configuration, isn't it ? What caused you to NOT have the Issue (when you replied me this Morning) ;) ?

Logs in Text Form if needed.

Still Error. Now I tried downloading the OCI that's marked as stable Release: https://quay.io/repository/fedora/fedora-coreos?tab=tags&tag=43.20251214.3.0 (on the right Side, behind the Popup, there is a small Green Line with 2 Dots / Images from 6 Days ago) Still results in Error though...

What would you like to know exactly ? Unfortunately it's been a while :(. If a container Creation fails (like this one did to me), everything gets aborted & erased. So I don't even know exactly where & what I was trying to create it :(. In this Regards, Proxmox VE is not very smart...

Old Thread but I'll add my 0.02$ just in case you are still looking for a Solution. In my Case, this can happen (mostly on a Backup Server) if I sent there a ZFS Snapshot WITHOUT specifying a -o mountpoint=/zdata/BACKUP/<HOST> Parameter when receiving it. If you forget to receive with the...

Alright, thanks :) . That's a valid Consideration for sure :). But to mind comes Scenario related to NIC Firmare / Driver which led to both Interfaces disappearing at the same Time (even though only one was being used). Rare Events but they do happen. I don't care about it and I'd like to go...

I think Expectations are on the Floor right now :p. You didn't read my Reply: What I provided is the Configuration of one Proxmox VE Host, but it's fairly representative across the Board with my other Servers. Depending on which specific Proxmox VE Host we are talking about, it might be...

It's unprivileged LXC :) . The weird Thing is that the Keys already exist inside that LXC Container ... It's completely non-consistent. Sometimes it happens, sometimes it doesn't.

Is it really necessary :p ? I feel most of your Comments are about VLAN, whereas the Problem I described is about the Bond (and potentially Bridge) Interface. 1. Right now pretty much only one Physical Interface is connected to a Managed L2 Switch. What I provided is the Configuration of one...

Is there one / several Configuration Errors on my Side ? If not, what is the best Way to solve this ? Create a dummy Network Interface that is always present and set that as Default (even though it makes no sense) ? EDIT 1: the following is a bit of a Hack but it works ;) Basically create a...

Unsure if they bring much more Information, but see the full Text Logs attached using Redirection of stdout + stderr to the respective File.

Using an Interface which does NOT exist for bond-primary Setting (enp1s0f0np0) Use ifdown bond0 to actually trigger the Issue: if the Bond already exists when the Configuration is reloaded, then the Bond will still exists afterwards. Test reloading Configuration using ifreload -avs Reload...

I started migrating from pure Bridge Network Setup towards Bond based Network Setup on several of my Hosts now, after I accidentally created a Network Loop by plugging in multiple NICs (physical Interface connected to vmbr0 in Proxmox Network Configuration) into a Physical Switch, all while...

@fabian: I faced the same a similar Error when trying to setup a Container based on fedora-coreos https://quay.io/repository/fedora/fedora-coreos?tab=tags Specifically the Image: quay.io/fedora/fedora-coreos:stable Unsure what is going on at the unpack Stage with the File...

There seems to be some Issue for a Fedora LXC Container. Specifically, SSH fails to start (as confirmed by ss -nlt) since nothing is listening on Port 22 after Boot. It seems that there is something related to sshd-keygen.target when used in an LXC Container. Disabling...

How is that relevant to the original Question ? You cannot have ZFS Module working in an LXC Container, at least not in an unprivileged one. Not sure if your Remark is applicable to a privileged LXC Container or if you had a KVM Virtual Machine. For an unprivileged Container the Solution...

I don't think it's possible. After all the -args Parameter is there for what is NOT implemented by Proxmox VE [yet] and since it feeds directly into QEMU Command Line, I believe you must use a Full Path. But why do you want to leave it attached ? My Usage at least is as a temporary LiveUSB...

Yeah, a very stupid one you could say :(. Weird that I didn't notice it until now o_O . Yet another Case of the Problem being between the Chair and the Screen. Sorry about that :(. I would have guessed that since the default none Cache Options for the Virtual Disk were used (writes ARE cached...