<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>chroot on System Administration, Hosting, Cloud and technologies in between</title>
    <link>https://dmsimard.com/tags/chroot/</link>
    <description>Recent content in chroot on System Administration, Hosting, Cloud and technologies in between</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 Jan 2016 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://dmsimard.com/tags/chroot/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Selinux, Python, virtualenv, chroot and ansible don&#39;t play nice.</title>
      <link>https://dmsimard.com/2016/01/08/selinux-python-virtualenv-chroot-and-ansible-dont-play-nice/</link>
      <pubDate>Fri, 08 Jan 2016 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2016/01/08/selinux-python-virtualenv-chroot-and-ansible-dont-play-nice/</guid>
      <description>The problem Aborting, target uses selinux but python bindings (libselinux-python) aren&#39;t installed!
Uh oh, have you seen that before ?
I bumped into an interesting issue recently when running Ansible from a RHEL derivative host.
It turns out that Ansible requires the package libselinux-python to be installed on hosts where Ansible is running file modules.
 If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible.</description>
    </item>
    
  </channel>
</rss>