Skip to content

In a systemD based Linux distribution chroot's are no longer as functional as they were in a sysV init enviornment. Systemd replaced this capability with the systemd namespace container. This repository uses ansible to initializes a Centos7 systemd container on a Centos7 host

License

Notifications You must be signed in to change notification settings

gspivey/systemd-namespace-container

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SystemD Container

Requires private key whose public key pair is in authorized_keys file of <user> <user> must also have a passwordless sudo -- sudo is not required if chroot/systemd container will be installed in a non privalged directory. -- path is chosen via chroot_basepath variable -- if you do not use sudo remove -b --become-user root from run command


Requirements

  • ansible 2.4

To log into container: Substitute below with your variables from deploy.yml Intial User is root, intial password is 1234 (CHANGE!) systemd-nspawn -bD <chroot_basepath>/<chrootname>

ansible-playbook -i hosts deploy.yml --private-key=<private-key> -u <user> -b --become-user root

About

In a systemD based Linux distribution chroot's are no longer as functional as they were in a sysV init enviornment. Systemd replaced this capability with the systemd namespace container. This repository uses ansible to initializes a Centos7 systemd container on a Centos7 host

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published