Recent content by Rob256

  1. R

    [SOLVED] can not 'chown' folder or file in unprivileged lxc container proxmox ve 6.2

    I have solved both by converting the Unprivileged lxc container to a Privileged lxc container, using the pct restore <nieuw_container_id> <my_backup_file> --storage <my_storage> By running freeipa in a privileged container, I was enable to chown again to ldap-users, and it also solved the ntp...
  2. R

    [SOLVED] can not 'chown' folder or file in unprivileged lxc container proxmox ve 6.2

    Had not thought of that , thanks. Yes that will work. chown with PAM user. chown with LDAP users generate ": Invalid argument" error. Also chown <LDAP-userID> The old instance was privileged lxc container. Do you think there is any chance, that this behaviour is related to the...
  3. R

    [SOLVED] can not 'chown' folder or file in unprivileged lxc container proxmox ve 6.2

    Acually , don't know. I installed only a few packages after the container was created, did it all as root. freeipa server-install created the admin user and others. No errors or warnings were flagged during installation of freeipa-server. Have had freeipa server installed on proxmox VE 4.3...
  4. R

    [SOLVED] can not 'chown' folder or file in unprivileged lxc container proxmox ve 6.2

    Thanks Fabian. Also found http://doc.ntp.org/4.1.0/miscopt.htm explaining options for ntp.conf file. Will experiment with "disable ntp" , this keeps the daemon running but does not adjust time. Unfortunately, also makes clients not to synchronize with the ntp server anymore. About the...
  5. R

    [SOLVED] can not 'chown' folder or file in unprivileged lxc container proxmox ve 6.2

    Hello, I recently created an lxc container in the proxmox 6.2 gui and installed a freeipa server on it. I used a centos 7 template for this. The ipa-server runs fine, but I see some unexpected behaviour in the logs and I found that I as root can not change owner or group from any created file...