Hey
Yesterday I did an upgrade of Proxmox from version 7 to 8. One of containers which has mount points defined started to make issues during boot due to special characters which one of the mount point has.
As far as I observed CT config file gets amended when I make a reboot of CT or PVE. Issue appears for mount point 1 (mp1) where originally path contains polish letter "ł". After CT reboot you can find below that this letter gets replaced by some weird characters "ÃÂ". I checked Proxmox locale, it's set to en_US.UTF-8. I also updated CT locale from C to C.utf8.
I didn't have such problems on Proxmox 6 or 7, I could use mount points with special characters without issues. I have no clue why config files gets amended when CT gets rebooted and paths are updated. Issue appears for both paths: origin path and desired path in CT, I did testing which confirms this.
Can someone help me with this? I'd rather stick with paths which may contain special characters, especially in case that they worked without single issue in older versions of Proxmox.
PVE version
CT config original
CT config after reboot
Yesterday I did an upgrade of Proxmox from version 7 to 8. One of containers which has mount points defined started to make issues during boot due to special characters which one of the mount point has.
As far as I observed CT config file gets amended when I make a reboot of CT or PVE. Issue appears for mount point 1 (mp1) where originally path contains polish letter "ł". After CT reboot you can find below that this letter gets replaced by some weird characters "ÃÂ". I checked Proxmox locale, it's set to en_US.UTF-8. I also updated CT locale from C to C.utf8.
I didn't have such problems on Proxmox 6 or 7, I could use mount points with special characters without issues. I have no clue why config files gets amended when CT gets rebooted and paths are updated. Issue appears for both paths: origin path and desired path in CT, I did testing which confirms this.
Can someone help me with this? I'd rather stick with paths which may contain special characters, especially in case that they worked without single issue in older versions of Proxmox.
PVE version
Code:
pve-manager/8.1.3/b46aac3b42da5d15 (running kernel: 6.5.11-7-pve)CT config original
Code:
arch: amd64
cores: 4
hostname: plex
memory: 8192
mp0: /mnt/pve/multimedia/Filmy,mp=/media/Filmy,ro=1
mp1: /mnt/pve/multimedia/Pozostałe,mp=/media/Pozostale,ro=1
net0: name=eth0,bridge=vmbr0,gw=10.0.0.1,hwaddr=46:05:00:62:F1:4B,ip=10.0.0.105/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=25G
swap: 512
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.hook.autodev: /var/lib/lxc/105/autodevCT config after reboot
Code:
arch: amd64
cores: 4
hostname: plex
memory: 8192
mp0: /mnt/pve/multimedia/Filmy,mp=/media/Filmy,ro=1
mp1: /mnt/pve/multimedia/PozostaÃÂe,mp=/media/Pozostale,ro=1
net0: name=eth0,bridge=vmbr0,gw=10.0.0.1,hwaddr=46:05:00:62:F1:4B,ip=10.0.0.105/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=25G
swap: 512
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.hook.autodev: /var/lib/lxc/105/autodev
Last edited:
