From 90ac906169da61b7339be648dc53f12a531bde0e Mon Sep 17 00:00:00 2001 From: Trent Palmer Date: Sun, 9 Jul 2017 20:44:10 -0700 Subject: [PATCH] minor correction docs/debian_nspawn_container_on_arch_for_testing_apache_configurations.md --- ..._on_arch_for_testing_apache_configurations.md | 3 ++- .../index.html | 3 ++- site/index.html | 2 +- site/mkdocs/search_index.json | 4 ++-- site/sitemap.xml | 16 ++++++++-------- 5 files changed, 15 insertions(+), 13 deletions(-) diff --git a/docs/debian_nspawn_container_on_arch_for_testing_apache_configurations.md b/docs/debian_nspawn_container_on_arch_for_testing_apache_configurations.md index 30cffad..4ef65d8 100644 --- a/docs/debian_nspawn_container_on_arch_for_testing_apache_configurations.md +++ b/docs/debian_nspawn_container_on_arch_for_testing_apache_configurations.md @@ -57,6 +57,7 @@ without dbus. In this case use the following sequence of commands. # start the container and login as root systemd-nspawn -b -D --network-bridge=br0 # bring up networking so you can install dbus +systemctl enable/start systemd-networkd # this is also a good time to install and configure locale apt install dbus locales # to configure locale @@ -88,7 +89,7 @@ tasksel install web-server # enable mod ssl a2enmod ssl ; systemctl restart apache2 # enable the default ssl test page -a2ensite /etc/apache2/sites-available/default-ssl.conf +a2ensite default-ssl.conf ; systemctl reload apache2 ``` You'll be up and running with the default self-signed certs. diff --git a/site/debian_nspawn_container_on_arch_for_testing_apache_configurations/index.html b/site/debian_nspawn_container_on_arch_for_testing_apache_configurations/index.html index 2b1afd4..68d31b2 100644 --- a/site/debian_nspawn_container_on_arch_for_testing_apache_configurations/index.html +++ b/site/debian_nspawn_container_on_arch_for_testing_apache_configurations/index.html @@ -172,6 +172,7 @@ without dbus. In this case use the following sequence of commands.

# start the container and login as root
 systemd-nspawn -b -D <container name> --network-bridge=br0 
 # bring up networking so you can install dbus
+systemctl enable/start systemd-networkd
 # this is also a good time to install and configure locale
 apt install dbus locales 
 # to configure locale 
@@ -198,7 +199,7 @@ tasksel install web-server
 # enable mod ssl
 a2enmod ssl ; systemctl restart apache2
 # enable the default ssl test page 
-a2ensite /etc/apache2/sites-available/default-ssl.conf
+a2ensite default-ssl.conf ; systemctl reload apache2

You'll be up and running with the default self-signed certs.

diff --git a/site/index.html b/site/index.html index 85b5f85..fda7e76 100644 --- a/site/index.html +++ b/site/index.html @@ -192,5 +192,5 @@ diff --git a/site/mkdocs/search_index.json b/site/mkdocs/search_index.json index 86bbcdc..691b922 100644 --- a/site/mkdocs/search_index.json +++ b/site/mkdocs/search_index.json @@ -182,12 +182,12 @@ }, { "location": "/debian_nspawn_container_on_arch_for_testing_apache_configurations/", - "text": "Debian Nspawn Container On Arch For Testing Apache Configurations\n\n\nBegin by exporting the environmental variable for your squid cacheing \nproxy. If you're deboostrapping Debian file systems, the best way to\nspeed this up is with squid.\n\n\nThe ArchWiki page for nspawn containers has a\n\nDebian/Ubuntu subsection\n\nObviously you're going to want to install debootstrap and debian-archive-keyring.\n\n\n# to create a Stretch Container\ncd /var/lib/machines \nmkdir \ndeboostrap stretch \n\n\n\n\nAfter some experimentation, perhaps this is the best time to write\nthe intended hostname into the container, and write any\napt-cacher or apt-cacher-ng proxies into /etc/apt/apt.conf \non the container.\n\n\ncp apt.conf /etc/apt/apt.conf \necho \"\" > /var/lib/machines//etc/hostname\n\n\n\n\nAnd then start the container, and set the root password.\n\n\n# boot in interactive mode\nsystemd-nspawn -D \n# set the passwd and logout\npassword \nlogout \n\n\n\n\nNow we can boot the container in non-interactive mode, either\nfrom the command line or using nspawn files. In either case \ndouble check that the your bind mounts have the correct permissions \nfrom inside the container.\n\n\n# for instance attached to a bridge interface br0 \nsystemd-nspawn -b -D --network-bridge=br0\n# or if you've set up a package cache \nsystemd-nspawn -b -D --network-bridge=br0 --bind=/var/cache/apt/archives\n\n\n\n\nAlternately, if you use an nspawn file, then you can use a command \nsimilar to the following to start it, you'll first need to \nboot the container from the command line and install dbus,\nbecause \nmachinectl shell\n and \nmachinectl login\n won't work \nwithout dbus. In this case use the following sequence of commands.\n\n\n# start the container and login as root\nsystemd-nspawn -b -D --network-bridge=br0 \n# bring up networking so you can install dbus\n# this is also a good time to install and configure locale\napt install dbus locales \n# to configure locale \ndpkg-reconfigure locales \npoweroff\n\n\n\n\nAfter this you can start the container with systemd, when \nusing an nspawn file.\n\n\nsystemctl start systemd-nspawn@\n\n\n\n\n# /etc/systemd/nspawn/.spawn \n[Files] \n# Bind=/var/cache/apt/archives \n\n[Network] \nbridge=br0 \n\n\n\n\nYou can use tasksel to install a web-server.\n\n\n# apache2 will immediately be listening on port 80\ntasksel install web-server\n# enable mod ssl\na2enmod ssl ; systemctl restart apache2\n# enable the default ssl test page \na2ensite /etc/apache2/sites-available/default-ssl.conf\n\n\n\n\nYou'll be up and running with the default self-signed certs.", + "text": "Debian Nspawn Container On Arch For Testing Apache Configurations\n\n\nBegin by exporting the environmental variable for your squid cacheing \nproxy. If you're deboostrapping Debian file systems, the best way to\nspeed this up is with squid.\n\n\nThe ArchWiki page for nspawn containers has a\n\nDebian/Ubuntu subsection\n\nObviously you're going to want to install debootstrap and debian-archive-keyring.\n\n\n# to create a Stretch Container\ncd /var/lib/machines \nmkdir \ndeboostrap stretch \n\n\n\n\nAfter some experimentation, perhaps this is the best time to write\nthe intended hostname into the container, and write any\napt-cacher or apt-cacher-ng proxies into /etc/apt/apt.conf \non the container.\n\n\ncp apt.conf /etc/apt/apt.conf \necho \"\" > /var/lib/machines//etc/hostname\n\n\n\n\nAnd then start the container, and set the root password.\n\n\n# boot in interactive mode\nsystemd-nspawn -D \n# set the passwd and logout\npassword \nlogout \n\n\n\n\nNow we can boot the container in non-interactive mode, either\nfrom the command line or using nspawn files. In either case \ndouble check that the your bind mounts have the correct permissions \nfrom inside the container.\n\n\n# for instance attached to a bridge interface br0 \nsystemd-nspawn -b -D --network-bridge=br0\n# or if you've set up a package cache \nsystemd-nspawn -b -D --network-bridge=br0 --bind=/var/cache/apt/archives\n\n\n\n\nAlternately, if you use an nspawn file, then you can use a command \nsimilar to the following to start it, you'll first need to \nboot the container from the command line and install dbus,\nbecause \nmachinectl shell\n and \nmachinectl login\n won't work \nwithout dbus. In this case use the following sequence of commands.\n\n\n# start the container and login as root\nsystemd-nspawn -b -D --network-bridge=br0 \n# bring up networking so you can install dbus\nsystemctl enable/start systemd-networkd\n# this is also a good time to install and configure locale\napt install dbus locales \n# to configure locale \ndpkg-reconfigure locales \npoweroff\n\n\n\n\nAfter this you can start the container with systemd, when \nusing an nspawn file.\n\n\nsystemctl start systemd-nspawn@\n\n\n\n\n# /etc/systemd/nspawn/.spawn \n[Files] \n# Bind=/var/cache/apt/archives \n\n[Network] \nbridge=br0 \n\n\n\n\nYou can use tasksel to install a web-server.\n\n\n# apache2 will immediately be listening on port 80\ntasksel install web-server\n# enable mod ssl\na2enmod ssl ; systemctl restart apache2\n# enable the default ssl test page \na2ensite default-ssl.conf ; systemctl reload apache2\n\n\n\n\nYou'll be up and running with the default self-signed certs.", "title": "Debian Nspawn Container On Arch For Testing Apache Configurations" }, { "location": "/debian_nspawn_container_on_arch_for_testing_apache_configurations/#debian-nspawn-container-on-arch-for-testing-apache-configurations", - "text": "Begin by exporting the environmental variable for your squid cacheing \nproxy. If you're deboostrapping Debian file systems, the best way to\nspeed this up is with squid. The ArchWiki page for nspawn containers has a Debian/Ubuntu subsection \nObviously you're going to want to install debootstrap and debian-archive-keyring. # to create a Stretch Container\ncd /var/lib/machines \nmkdir \ndeboostrap stretch After some experimentation, perhaps this is the best time to write\nthe intended hostname into the container, and write any\napt-cacher or apt-cacher-ng proxies into /etc/apt/apt.conf \non the container. cp apt.conf /etc/apt/apt.conf \necho \"\" > /var/lib/machines//etc/hostname And then start the container, and set the root password. # boot in interactive mode\nsystemd-nspawn -D \n# set the passwd and logout\npassword \nlogout Now we can boot the container in non-interactive mode, either\nfrom the command line or using nspawn files. In either case \ndouble check that the your bind mounts have the correct permissions \nfrom inside the container. # for instance attached to a bridge interface br0 \nsystemd-nspawn -b -D --network-bridge=br0\n# or if you've set up a package cache \nsystemd-nspawn -b -D --network-bridge=br0 --bind=/var/cache/apt/archives Alternately, if you use an nspawn file, then you can use a command \nsimilar to the following to start it, you'll first need to \nboot the container from the command line and install dbus,\nbecause machinectl shell and machinectl login won't work \nwithout dbus. In this case use the following sequence of commands. # start the container and login as root\nsystemd-nspawn -b -D --network-bridge=br0 \n# bring up networking so you can install dbus\n# this is also a good time to install and configure locale\napt install dbus locales \n# to configure locale \ndpkg-reconfigure locales \npoweroff After this you can start the container with systemd, when \nusing an nspawn file. systemctl start systemd-nspawn@ # /etc/systemd/nspawn/.spawn \n[Files] \n# Bind=/var/cache/apt/archives \n\n[Network] \nbridge=br0 You can use tasksel to install a web-server. # apache2 will immediately be listening on port 80\ntasksel install web-server\n# enable mod ssl\na2enmod ssl ; systemctl restart apache2\n# enable the default ssl test page \na2ensite /etc/apache2/sites-available/default-ssl.conf You'll be up and running with the default self-signed certs.", + "text": "Begin by exporting the environmental variable for your squid cacheing \nproxy. If you're deboostrapping Debian file systems, the best way to\nspeed this up is with squid. The ArchWiki page for nspawn containers has a Debian/Ubuntu subsection \nObviously you're going to want to install debootstrap and debian-archive-keyring. # to create a Stretch Container\ncd /var/lib/machines \nmkdir \ndeboostrap stretch After some experimentation, perhaps this is the best time to write\nthe intended hostname into the container, and write any\napt-cacher or apt-cacher-ng proxies into /etc/apt/apt.conf \non the container. cp apt.conf /etc/apt/apt.conf \necho \"\" > /var/lib/machines//etc/hostname And then start the container, and set the root password. # boot in interactive mode\nsystemd-nspawn -D \n# set the passwd and logout\npassword \nlogout Now we can boot the container in non-interactive mode, either\nfrom the command line or using nspawn files. In either case \ndouble check that the your bind mounts have the correct permissions \nfrom inside the container. # for instance attached to a bridge interface br0 \nsystemd-nspawn -b -D --network-bridge=br0\n# or if you've set up a package cache \nsystemd-nspawn -b -D --network-bridge=br0 --bind=/var/cache/apt/archives Alternately, if you use an nspawn file, then you can use a command \nsimilar to the following to start it, you'll first need to \nboot the container from the command line and install dbus,\nbecause machinectl shell and machinectl login won't work \nwithout dbus. In this case use the following sequence of commands. # start the container and login as root\nsystemd-nspawn -b -D --network-bridge=br0 \n# bring up networking so you can install dbus\nsystemctl enable/start systemd-networkd\n# this is also a good time to install and configure locale\napt install dbus locales \n# to configure locale \ndpkg-reconfigure locales \npoweroff After this you can start the container with systemd, when \nusing an nspawn file. systemctl start systemd-nspawn@ # /etc/systemd/nspawn/.spawn \n[Files] \n# Bind=/var/cache/apt/archives \n\n[Network] \nbridge=br0 You can use tasksel to install a web-server. # apache2 will immediately be listening on port 80\ntasksel install web-server\n# enable mod ssl\na2enmod ssl ; systemctl restart apache2\n# enable the default ssl test page \na2ensite default-ssl.conf ; systemctl reload apache2 You'll be up and running with the default self-signed certs.", "title": "Debian Nspawn Container On Arch For Testing Apache Configurations" }, { diff --git a/site/sitemap.xml b/site/sitemap.xml index 9f44677..674f45b 100644 --- a/site/sitemap.xml +++ b/site/sitemap.xml @@ -4,7 +4,7 @@ / - 2017-07-04 + 2017-07-09 daily @@ -12,7 +12,7 @@ /serve_and_share_apps_from_your_phone_with_fdroid/ - 2017-07-04 + 2017-07-09 daily @@ -20,7 +20,7 @@ /nspawn/ - 2017-07-04 + 2017-07-09 daily @@ -28,7 +28,7 @@ /debian_nspawn_container_on_arch_for_testing_apache_configurations/ - 2017-07-04 + 2017-07-09 daily @@ -36,7 +36,7 @@ /dynamic_cacheing_nginx_reverse_proxy_for_pacman/ - 2017-07-04 + 2017-07-09 daily @@ -44,7 +44,7 @@ /arch_redis_nspawn/ - 2017-07-04 + 2017-07-09 daily @@ -52,7 +52,7 @@ /arch_postgresql_nspawn/ - 2017-07-04 + 2017-07-09 daily @@ -60,7 +60,7 @@ /self_signed_certs/ - 2017-07-04 + 2017-07-09 daily