Plesk for Linux kb: technical ABT: Group B
- Plesk for Linux
Plesk Update fails with one of the following error messages:
CONFIG_TEXT: error: unpacking of archive failed on file /usr/local/psa/admin/sbin/deployer: cpio: rename failed - Operation not permitted
CONFIG_TEXT: error: unpacking of archive failed on file /usr/local/psa/admin/sbin/deployer: cpio: rename failed - Permission denied
SELinux security module is in the enforcing mode:
The file mentioned in the error message has incorrect SELinux context.
Connect to the Plesk server via SSH.
Restore SELinux context on the file from the error message. In this example, the file is
# restorecon -v -F /usr/local/psa/admin/sbin/deployer
Rerun Plesk Update:
# plesk installer update
I try to upgrade Plesk Onyx to Plesk Obisidan on LXC container. I run /usr/local/psa/admin/bin/autoinstaller and after few steps I got
chcon: failed to change context of '/usr/local/psa/bin/yum_install' to
'system_u:object_r:rpm_exec_t:s0': Operation not permitted
I can continue the upgrade anyway but configuration of all server will
be broken, especially httpd. I think that problem is because of LXC unpriviliged container.
Can I solve this problem?
Product: Plesk Onyx 17.8.11 Update #67 , last updated at Sept 11, 2019 04:51 AM
Virtualization: unpriviliged LXC container and Proxmox 6
Please let me clarify that Plesk installation on unprivileged LXC container was not tested by Plesk and is not supported. The installation could be performed on your risk.
I suggest reviewing security policies on the server or contacting the hosting provider for assistance.
In general, I found the information about the issue of installing httpd service on an unprivileged container. The links below can be helpful to you:
thank you for your information. It was very helpful. Did now anyone from you on Plesk tested installation on unprivileged LXC container? Cause I install version Onyx 17 on CentOS 7 then upgrade to 17.8 and then upgrade to Obsidion 18.0 without any problem. What kind of problems can we expect at all with unprivileged LXC container?
Generally, everything should go smoothly.
In case of issues, feel free o submit a request for support.
thank you for your information. Just keep on going that Plesk will support unpriviliged LXC containers in the future. I work at a hosting company and we are using Plesk for a long time. We will be using Plesk in LXV virtualization to. So we need a full support of unpriviliged LXC containers. I will let you know if we will have some problems using Plesk with unpriviliged LXC containers. Thanks again!!!
Please sign in to leave a comment.