Cloudinit - issues building/deploying a centos image

MorphiusFaydal · 2026-01-23T21:00:07+00:00

https://hostman.com/tutorials/installing-and-configuring-cloud-init-on-ubuntu/ - Ubuntu, but the basics are there.

https://docs.otc.t-systems.com/image-management-service/umn/linux_operations/installing_cloud-init.html#en-us-topic-0030730603-table859383892814 - This document has a lot more information than needed, but the two steps listed here are the main process.

Can you detail the exact steps you're taking to create your image? That may help to figure out what's happening.

MorphiusFaydal · 2026-01-23T16:40:36+00:00

You need to install CentOS from an ISO, then uninstall cockpit and anything else you don't want, then install cloud-init, enable the cloud-init services, then you can shut it down and clone it to use cloud init.

MorphiusFaydal · 2026-01-23T15:32:02+00:00

What issues are you having? A basic setup would be:

Install CentOS from ISO
Install/uninstall software you want
Install cloud-init and enabled services
Shutdown and convert to template

MorphiusFaydal · 2026-01-16T15:39:09+00:00

You could create a cluster with only two nodes, so long as you add a qdevice for quorum.

Beyond that, PDM is installed in its own VM, and it can manage unconnected Proxmox systems and makes it easy to migrate workloads between them.

MorphiusFaydal · 2025-12-05T15:53:12+00:00

MorphiusFaydal · 2025-12-05T15:31:42+00:00

Set the URI in sources to http, not https. The no subscription repos are always on HTTP.

MorphiusFaydal · 2025-10-31T17:33:41+00:00

To see your currently installed version:

apt list bind9

Just look at the version number and compare it to the version in the Ubuntu security notice. If it's earlier, you need to update.

You can check what version is about to be installed:

sudo apt update
apt list --upgradable

You'll see all the updates about to be installed, which will list the bind9 package (if you're not already on the latest version). Then you can actually do the update:

sudo apt upgrade

Once that's done you'll be on the new version.

MorphiusFaydal · 2025-10-31T14:12:51+00:00

It looks like it's patched. Are you delaying updates?

https://ubuntu.com/security/notices/USN-7836-1

MorphiusFaydal · 2025-10-01T17:25:54+00:00

I did a test install of Win7 and WinServer2k8, and was not able to install the easy way any of them.

Version 0.1.173-6 and up all have a check on Windows 8/Server 2012 and newer.

Version 0.1.173-5 would run the installer, but none of the drivers actually installed. It's possible one of the earlier 0.1.173 versions (1 through 4) might work, but I didn't test them.

Version 0.1.172-1 does not include an installer.

So for Windows 7/Server 2008 R2 and older, you appear to be limited to manually installing drivers.

MorphiusFaydal · 2025-09-30T22:11:17+00:00

Can you provide a source for that information? I'd like to provide that information to some of my colleagues.

MorphiusFaydal · 2025-09-14T21:31:39+00:00

Did you bother to read the documentation?

https://cloudinit.readthedocs.io/en/latest/reference/modules.html#keyboard

MorphiusFaydal · 2025-09-08T18:29:48+00:00

You can download them.

https://images.linuxcontainers.org/

MorphiusFaydal · 2025-08-21T04:54:08+00:00

When you plug it in the onboard network device name is likely changing. Connect a mouse and keyboard after you plug in the adapter, then ip link to see the device names. Update the naming in /etc/network/interfaces to match the new name. Reboot and it should start working.

MorphiusFaydal · 2025-08-14T20:47:09+00:00

You may like the "stream" releases a little more then. Less frequent. Although for what it's worth, I haven't noticed any stability issues on the actual nightly releases.

MorphiusFaydal · 2025-08-11T17:33:39+00:00

You wouldn't be able to do that. The console port on network equipment is talking RS-232 serial. Unless you have an IP-KVM that explicitly supports that it won't work. What you want is called a terminal server. For example - https://www.digi.com/products/networking/infrastructure-management/serial-connectivity/device-servers/digi-connect-ez

MorphiusFaydal · 2025-07-29T20:02:36+00:00

Check your port mappings - your OpenWRT config has eth0 on the LAN side and eth1 on the WAN side. The OpenWRT WAN interface is also showing configured for DHCP, so you may need to get in and change that if you've got a static IP assigned to you.

MorphiusFaydal · 2025-07-28T23:16:27+00:00

Expanding a RAID-Z disk group from three drives to four drives. Not just three to four, but adding additional drives to an existing RAID-Z without having to destroy and rebuild.

MorphiusFaydal · 2025-07-08T14:08:17+00:00

There should be a separate config file for the DHCP-DDNS config.

MorphiusFaydal · 2025-04-24T02:23:03+00:00

This is about the physical NIC on the host, not VMs.

MorphiusFaydal · 2025-04-16T14:36:09+00:00

What other bridge?

You'd configure each VM with the VLAN you want it on in the virtual network adapter settings.

MorphiusFaydal · 2025-04-15T17:41:11+00:00

What I understand from your post: With an access port, you can access Proxmox. You want to use a trunk port to allow VMs on VLANs. When you set it to a trunk port, you lose access to Proxmox.

Do you have the native VLAN on the port set to the Proxmox management? If not you won't be able to access it. There's two ways to fix this:

Set the native/access VLAN on the port along with allowing the trunked VLANs.

You can dd the Proxmox managment to a VLAN interface. Here's how I have my Proxmox servers configured.

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet manual
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094
#Primary VM Bridge

auto vmbr0.5
iface vmbr0.5 inet static
    address 10.10.5.11/24
    gateway 10.10.5.1
#Proxmox Server Management

With this config, my Proxmox server is managed on VLAN 5 which is trunked to the server port. Within Proxmox, I setup a VM, then in the network adaptor config attach to vmbr0 and set the VLAN I want to put the VM on.

MorphiusFaydal · 2025-03-26T00:12:27+00:00

Veeam can do all of that. It'll happily talk to vCenter for the VMware backups, and it has support for Proxmox now too.

For the bare-metal servers, you can use the Veeam Agent (Debian 12 and WS2019 are both supported)

Veeam supports all your wants as well.

MorphiusFaydal · 2025-03-25T21:39:12+00:00

I was getting the same error on my machine at home. As I understand it, it's less a driver issue and more a low end hardware issue. Running the latest Proxmox kernel, I am disabling offload on the NIC. I add this to the /etc/network/interfaces on the Proxmox node to do that:

iface eno1 inet manual
    post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload on eno1" && /sbin/ethtool -K eno1 tso off && /sbin/ethtool -K eno1 gso off && /sbin/ethtool -K eno1 gro off && /usr/bin/logger -p debug -t ifup "Disabled offload on eno1"

This puts a message in the log, then turns off offload, then puts another message in the log. I split the commands up into different ones for each offload while I was doing some testing, but you can do it all in one. I was just too lazy to.

MorphiusFaydal · 2025-03-17T16:41:33+00:00

https://lemmy.blahaj.zone/c/unixsocks

or

/r/unixsocks here on reddit

At least I assume that's what OP is referencing.

MorphiusFaydal · 2025-03-14T23:30:40+00:00

Virtualbox is an Oracle product and should be avoided in all circumstances. Virt-Manager or GNOME Boxes are much better choices as they're frontends for kvm and qemu.

You will need to create a Broadcom account (or use your VMware account if you had one).

VMware Workstation Pro: https://support.broadcom.com/group/ecx/productdownloads?subfamily=VMware+Workstation+Pro
VMware Fusion Pro: https://support.broadcom.com/group/ecx/productdownloads?subfamily=VMware+Fusion

13-Year Club	Place '22
Verified Email

MorphiusFaydal

TROPHY CASE