LXC Host - Revision history

Michael.mast: /* Troubleshooting */

2018-09-22T16:33:01Z

Troubleshooting

Michael.mast: /* CentOS 7 */

2018-09-22T15:38:27Z

CentOS 7

Michael.mast: /* CentOS 7 */

2018-09-22T15:16:47Z

CentOS 7

Michael.mast: /* CentOS 7 */

2018-09-22T15:11:43Z

CentOS 7

Michael.mast: /* CentOS 7 */

2017-03-18T17:23:20Z

CentOS 7

Michael.mast: /* CentOS 7 */

2017-03-18T16:55:31Z

CentOS 7

Michael.mast: Created page with "==CentOS 7== http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/https://stgraber.org/2013/12/27/lxc-1-0-container-storage/"

2017-03-18T16:42:05Z

Created page with "==CentOS 7== <ref>http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/</ref><ref>https://stgraber.org/2013/12/27/lxc-1-0-container-storage/</ref>"

New page

==CentOS 7==
<ref>http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/</ref><ref>https://stgraber.org/2013/12/27/lxc-1-0-container-storage/</ref>

← Older revision		Revision as of 16:33, 22 September 2018
Line 100:		Line 100:
	Active: inactive (dead)		Active: inactive (dead)

		+	</pre>
		+	====SELinux====
		+	I am not entirely sure the best way to handle this. Though I am a huge supporter of using SELinux, I am no expert on implementation.
		+	<br>
		+	After creating a new container, I ran inter the following errors
		+	<pre>
		+	sed: can't read /raid5/services/containers/test3/rootfs/etc/init/tty.conf: No such file or directory
		+	Storing root password in '/raid5/services/containers/test3/tmp_root_pass'
		+	chpasswd: cannot open /etc/passwd
		+	Expiring password for user root.
		+	passwd: Libuser error at line: 413 - Error replacing `/etc/passwd': Permission denied.
		+	passwd: Error
		+	sed: can't read /raid5/services/containers/test3/rootfs/etc/rc.sysinit: No such file or directory
		+	sed: can't read /raid5/services/containers/test3/rootfs/etc/rc.d/rc.sysinit: No such file or directory
		+	</pre>
		+	Because lxc copies the rootfs from cache, I think this messes up the context on the files. Digging through the audit.log I found passwd having problems accessing the container files.
		+	<pre>
		+	[root@nas ~]# : > /var/log/audit/audit.log
		+	[root@nas ~]# lxc-create -n test3 -t centos
		+	...
		+	[root@nas ~]# grep passwd /var/log/audit/audit.log
		+	type=AVC msg=audit(1537633138.649:5348): avc: denied { read write } for pid=18611 comm="chpasswd" path="/raid5/services/containers/test2/partial" dev="zfs" ino=176109 scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:default_t:s0 tclass=file
		+	...
		+	[root@nas ~]# chroot /raid5/services/containers/test3/rootfs 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
		+	</pre>
		+	Since all of these alerts were generated during the creation of the container, I felt comfortable enough using audit2allow to allow access. Though looking at the output it may not have been a good idea. Time will tell :-P
		+	<pre>
		+	[root@nas ~]# grep passwd /var/log/audit/audit.log \| audit2allow
		+
		+
		+	#============= passwd_t ==============
		+	allow passwd_t default_t:chr_file read;
		+
		+	#!!!! WARNING: 'default_t' is a base type.
		+	allow passwd_t default_t:dir read;
		+
		+	#!!!! WARNING: 'default_t' is a base type.
		+	allow passwd_t default_t:file { read write };
		+
		+	#!!!! WARNING: 'etc_t' is a base type.
		+	allow passwd_t etc_t:file { unlink write };
		+	[root@nas ~]# restorecon -R /raid5/services/containers
		+	[root@nas ~]# chroot /raid5/services/containers/test3/rootfs passwd
		+	Changing password for user root.
		+	New password:
		+	BAD PASSWORD: The password is shorter than 8 characters
		+	Retype new password:
		+	passwd: all authentication tokens updated successfully.
	</pre>		</pre>

@@ Line 7: / Line 7: @@
 [root@web ~]# yum install lxc lxc-templates
 </pre>
 ===ImportError: No module named 'lxc'===
 I ran into a problem when trying to list my containers.
 <pre>
@@ Line 81: / Line 88: @@
 I think we have success!
-===Unit lxc.service could not be found===
+====Unit lxc.service could not be found====
 When I was first installing LXC, my server ended up dying on me. After moving drives to a new system I found LXC to be corrupted. A re-install was needed.
 <pre>

← Older revision		Revision as of 15:16, 22 September 2018
Line 80:		Line 80:
	</pre>		</pre>
	I think we have success!		I think we have success!
		+
		+	===Unit lxc.service could not be found===
		+	When I was first installing LXC, my server ended up dying on me. After moving drives to a new system I found LXC to be corrupted. A re-install was needed.
		+	<pre>
		+	[root@nas ~]# systemctl status lxc
		+	Unit lxc.service could not be found.
		+	[root@nas ~]# yum reinstall $(yum list installed \| grep lxc \| awk '{print $1}')
		+	...
		+	[root@nas ~]# systemctl status lxc
		+	● lxc.service - LXC Container Initialization and Autoboot Code
		+	Loaded: loaded (/usr/lib/systemd/system/lxc.service; disabled; vendor preset: disabled)
		+	Active: inactive (dead)
		+
		+	</pre>

@@ Line 1: / Line 1: @@
 ==CentOS 7==
 <ref>http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/</ref><ref>https://stgraber.org/2013/12/27/lxc-1-0-container-storage/</ref>
 <pre>
@@ Line 5: / Line 6: @@
 [root@web ~]# yum install debootstrap perl libvirt
 [root@web ~]# yum install lxc lxc-templates
 </pre>

@@ Line 3: / Line 3: @@
 <pre>
 [root@web ~]# yum install epel-release
 </pre>

← Older revision		Revision as of 16:55, 18 March 2017
Line 1:		Line 1:
	==CentOS 7==		==CentOS 7==
	<ref>http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/</ref><ref>https://stgraber.org/2013/12/27/lxc-1-0-container-storage/</ref>		<ref>http://www.tecmint.com/install-create-run-lxc-linux-containers-on-centos/</ref><ref>https://stgraber.org/2013/12/27/lxc-1-0-container-storage/</ref>
		+	<pre>
		+	[root@web ~]# yum install epel-release
		+
		+	</pre>