Description of problem: [root@fedex machines]# systemd-nspawn -D /var/lib/machines/test1 Spawning container test1 on /var/lib/machines/test1. Press ^] three times within 1s to kill container. -bash-4.3# passwd Changing password for user root. New password: BAD PASSWORD: The password is shorter than 8 characters Retype new password: passwd: Authentication token manipulation error SELinux is preventing passwd from 'read' accesses on the chr_file urandom. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that passwd should be allowed read access on the urandom chr_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep passwd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 Target Context unconfined_u:object_r:user_tmp_t:s0 Target Objects urandom [ chr_file ] Source passwd Source Path passwd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-155.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-12-17 22:58:15 CET Last Seen 2015-12-17 22:58:15 CET Local ID a6eb4750-68af-4481-b791-fdb970f71cd8 Raw Audit Messages type=AVC msg=audit(1450389495.865:1169): avc: denied { read } for pid=4660 comm="passwd" name="urandom" dev="tmpfs" ino=251201 scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=chr_file permissive=0 Hash: passwd,passwd_t,user_tmp_t,chr_file,read Version-Release number of selected component: selinux-policy-3.13.1-155.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.6-301.fc23.x86_64 type: libreport
In order to run selinux inside of a container, you need to make sure all of the content is labeled correctly or run with a type that will not transition. systemd-nspawn -Z system_u:system_r:spc_t:s0 might work Or try unconfined_service_t or something like that. It looks like you have partial labels inside of your container, for example passwd must be labeled as passwd_exec_t inside the container.
chcon -R system_u:object_r:svirt_sandbox_file_t:s0 /var/lib/machines/test1 semanage fcontext -a -t virtd_exec_t `which systemd-nspawn` restorecon `which systemd-nspawn` This is what will do the job.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.