[lxc-devel] [linuxcontainers.org/master] Replace Bootstrap with Vanilla as the CSS framework
anthonydillon on Github
lxc-bot at linuxcontainers.org
Wed Nov 1 11:16:45 UTC 2017
A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 682 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20171101/12579b8b/attachment.bin>
-------------- next part --------------
From 50e47ddbf10d8e51e2cfc8a11f556aca69dd7a3a Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Wed, 11 Oct 2017 21:48:47 +0100
Subject: [PATCH 1/8] Remove bootstrap and apply Vanilla
---
content/index.html | 154 +++---
content/lxd/try-it.html | 1005 +++++++++++++++++++-------------------
generate | 1 +
static/css/local.css | 233 +--------
templates/common/base.tpl.html | 25 +-
templates/common/footer.tpl.html | 25 +-
templates/common/header.tpl.html | 47 +-
templates/downloads.tpl.html | 4 +
templates/markdown-page.tpl.html | 8 +
9 files changed, 672 insertions(+), 830 deletions(-)
create mode 100644 templates/markdown-page.tpl.html
diff --git a/content/index.html b/content/index.html
index 652092a..a41f05c 100644
--- a/content/index.html
+++ b/content/index.html
@@ -1,88 +1,104 @@
-<h2>LinuxContainers.org <span class="text-muted">Infrastructure for container projects.</span></h2>
-<div class="large_content">
- <p><img src="/static/img/containers.png"
- alt="logo"/>
- linuxcontainers.org is the umbrella project behind LXC,
+
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>Infrastructure for container projects.</h1>
+ <p>linuxcontainers.org is the umbrella project behind LXC,
LXD and LXCFS.</p>
- <p>The goal is to offer a distro and vendor neutral environment
- for the development of Linux container technologies.</p>
+ <p>The goal is to offer a distro and vendor neutral environment
+ for the development of Linux container technologies.</p>
- <p>Our main focus is system containers. That is, containers which
- offer an environment as close as possible as the one you'd get from a
- VM but without the overhead that comes with running a separate
- kernel and simulating all the hardware.</p>
+ <p>Our main focus is system containers. That is, containers which
+ offer an environment as close as possible as the one you'd get from a
+ VM but without the overhead that comes with running a separate
+ kernel and simulating all the hardware.</p>
+ </div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>Active projects</h2>
-<hr/>
-<h2>Active projects</h2>
-<div class="row">
- <div class="col-md-4">
- <h3>LXC</h3>
- <p>LXC is the well known set of tools, templates,
- library and language bindings. It's pretty low
- level, very flexible and covers just about every
- containment feature supported by the upstream
- kernel.</p>
- <p>LXC is production ready with LXC 1.0 getting 5
- years of security updates and bugfixes
- (until April 2019).</p>
- <p><a class="btn btn-primary" href="/lxc/introduction/" role="button">Learn more »</a></p>
+ </div>
</div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>LXC is the well known set of tools, templates,
+ library and language bindings. It's pretty low
+ level, very flexible and covers just about every
+ containment feature supported by the upstream
+ kernel.</p>
+ <p>LXC is production ready with LXC 1.0 getting 5
+ years of security updates and bugfixes
+ (until April 2019).</p>
+ <p><a class="p-button" href="/lxc/introduction/" role="button">Learn more</a></p>
+ </div>
- <div class="col-md-4">
- <h3>LXD</h3>
- <p>LXD is the new LXC experience. It offers a
- completely fresh and intuitive user experience
- with a single command line tool to manage your
- containers. Containers can be managed over the
- network in a transparent way through a REST API.
- It also works with large scale deployments by
- integrating with OpenStack.</p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>LXD is the new LXC experience. It offers a
+ completely fresh and intuitive user experience
+ with a single command line tool to manage your
+ containers. Containers can be managed over the
+ network in a transparent way through a REST API.
+ It also works with large scale deployments by
+ integrating with OpenStack.</p>
- <p>
- <a class="btn btn-primary" href="/lxd/try-it/" role="button">Try it »</a>
- <a class="btn btn-primary" href="/lxd/introduction/" role="button">Learn more »</a>
- </p>
- </div>
+ <p>
+ <a class="p-button--positive" href="/lxd/try-it/" role="button">Try it</a>
+ <a class="p-button" href="/lxd/introduction/" role="button">Learn more</a>
+ </p>
+ </div>
- <div class="col-md-4">
- <h3>LXCFS</h3>
- <p>Userspace (FUSE) filesystem offering two main things:
- <ul>
- <li>Overlay files for cpuinfo, meminfo, stat and uptime.</li>
- <li>A cgroupfs compatible tree allowing unprivileged writes.</li>
- </ul>
- </p>
+ <div class="p-card col-4">
+ <h3>LXCFS</h3>
+ <p>Userspace (FUSE) filesystem offering two main things:
+ <ul>
+ <li>Overlay files for cpuinfo, meminfo, stat and uptime.</li>
+ <li>A cgroupfs compatible tree allowing unprivileged writes.</li>
+ </ul>
+ </p>
- <p>It's designed to workaround the shortcomings of procfs, sysfs
- and cgroupfs by exporting files which match what a system
- container user would expect.</p>
+ <p>It's designed to workaround the shortcomings of procfs, sysfs
+ and cgroupfs by exporting files which match what a system
+ container user would expect.</p>
- <p><a class="btn btn-primary" href="/lxcfs/introduction/" role="button">Learn more »</a></p>
+ <p><a class="p-button" href="/lxcfs/introduction/" role="button">Learn more</a></p>
+ </div>
</div>
</div>
-<hr/>
-<h2>Deprecated projects</h2>
-<div class="row">
- <div class="col-md-6">
- <h3>CGManager</h3>
- <p>CGManager is our cgroup manager daemon. It's
- designed to allow nested unprivileged containers
- to still be able to create and manage their
- cgroups through a DBus API.</p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ <h2>Deprecated projects</h2>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-6">
+ <h3>CGManager</h3>
+ <p>CGManager is our cgroup manager daemon. It's
+ designed to allow nested unprivileged containers
+ to still be able to create and manage their
+ cgroups through a DBus API.</p>
- <p>CGManager was used by default with LXC in
- Ubuntu since April 2014 and then by other
- distributions as they started needing working
- unprivileged containers.</p>
+ <p>CGManager was used by default with LXC in
+ Ubuntu since April 2014 and then by other
+ distributions as they started needing working
+ unprivileged containers.</p>
- <p>It has now been deprecated in favor of the CGroup namespace
- in recent Linux kernels. On older kernels, LXCFS still offers
- a cgroupfs emulation that can be used instead of cgmanager
- and is more widely compatible with existing userspace.</p>
+ <p>It has now been deprecated in favor of the CGroup namespace
+ in recent Linux kernels. On older kernels, LXCFS still offers
+ a cgroupfs emulation that can be used instead of cgmanager
+ and is more widely compatible with existing userspace.</p>
- <p><a class="btn btn-primary" href="/cgmanager/introduction/" role="button">Learn more »</a></p>
+ <p><a class="btn btn-primary" href="/cgmanager/introduction/" role="button">Learn more ›</a></p>
+ </div>
</div>
</div>
diff --git a/content/lxd/try-it.html b/content/lxd/try-it.html
index 7aeaaeb..7eec9e4 100644
--- a/content/lxd/try-it.html
+++ b/content/lxd/try-it.html
@@ -3,538 +3,545 @@
<script src="/static/js/term.js" type="text/javascript"></script>
<script src="/static/js/bootstrap-rating.min.js" type="text/javascript"></script>
<script src="/static/js/tryit.js" type="text/javascript"></script>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-12">
+ <noscript>
+ <div class="panel panel-danger">
+ <div class="panel-heading">JavaScript required</div>
+
+ <div class="panel-body">
+ <p>The LXD demo service client is entirely JavaScript based.</p>
+
+ <p>It appears the your web browser doesn't support JavaScript or
+ that you or an extension you installed is disabling
+ JavaScript for this site.</p>
+
+ <p>To use this service, you will need to enable JavaScript support
+ and refresh the page.</p>
+ </div>
+ </div>
+ </noscript>
-<noscript>
- <div class="panel panel-danger">
- <div class="panel-heading">JavaScript required</div>
-
- <div class="panel-body">
- <p>The LXD demo service client is entirely JavaScript based.</p>
-
- <p>It appears the your web browser doesn't support JavaScript or
- that you or an extension you installed is disabling
- JavaScript for this site.</p>
-
- <p>To use this service, you will need to enable JavaScript support
- and refresh the page.</p>
- </div>
- </div>
-</noscript>
-
-<div class="panel panel-success" id="tryit_status_panel" style="display:none">
- <div class="panel-heading">Server status</div>
- <div class="panel-body" id="tryit_online_message" style="display:none">
- You are connected over: <span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
- The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span>
- </div>
-
- <div class="panel-body" id="tryit_maintenance_message" style="display:none">
- The demo service is currently down for maintenance and should be
- back online in a few minutes.
- </div>
-
- <div class="panel-body" id="tryit_unreachable_message" style="display:none">
- Your browser couldn't reach the demo server.<br />
- This is either (most likely) because of a firewall or proxy
- issue on your side or because of a network, power or other catastrophic
- server side failure.
- </div>
-</div>
-
-<div class="panel panel-primary" id="tryit_terms_panel" style="display:none">
- <div class="panel-heading">Terms of service</div>
- <div class="panel-body" id="tryit_terms"></div>
-</div>
-
-<div class="panel panel-warning" id="tryit_start_panel" style="display:none">
- <div class="panel-heading">Start</div>
- <div class="panel-body">
- <button class="btn btn-default btn-lg" id="tryit_accept" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-ok"></span>
- I have read and accept the terms of service above
- </button>
-
- <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
- <p>
- <big>Starting the container...</big>
- </p>
- <p>
- <div class="large spinner"></div>
- </p>
- </div>
- </div>
-</div>
-
-<div class="panel panel-success" id="tryit_info_panel" style="display:none">
- <div class="panel-heading">Container information</div>
- <table class="table" style="padding-left: 15px;">
- <tr id="tryit_lxd_row">
- <th>Remote LXD</th>
- <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
- </tr>
-
- <tr id="tryit_clock">
- <th>Remaining time</th>
- <td><span class="minutes"></span> minutes, <span class="seconds"></span> seconds</td>
- </tr>
- </table>
-</div>
-
-<div class="panel panel-primary" id="tryit_console_panel" style="display:none">
- <div class="panel-heading">Terminal</div>
- <div id="tryit_console" style="background-color:black;"></div>
-
- <button class="btn btn-default btn-lg" id="tryit_console_reconnect" type="button" style="display:none">
- <span aria-hidden="true" class="glyphicon glyphicon-repeat"></span>
- Reconnect
- </button>
-</div>
-
-<div class="panel panel-warning" id="tryit_examples_panel" style="display:none">
- <div class="panel-heading"><a data-toggle="collapse" class="text" href="#tryit_examples_collapse">Step by step instructions</a></div>
- <div class="panel-body collapse in" id="tryit_examples_collapse">
- <ul class="nav nav-tabs" style="display:none">
- <li class="active"><a href="#introduction" data-toggle="tab">Introduction</a></li>
- <li><a href="#first-container" data-toggle="tab">Your first container</a></li>
- <li><a href="#limiting-resources" data-toggle="tab">Limiting resources</a></li>
- <li><a href="#snapshots" data-toggle="tab">Snapshots</a></li>
- <li><a href="#creating-images" data-toggle="tab">Creating images</a></li>
- <li><a href="#container-files" data-toggle="tab">Accessing files from the container</a></li>
- <li><a href="#image-server" data-toggle="tab">Use a remote image server</a></li>
- <li><a href="#remote-lxd" data-toggle="tab">Interact with remote LXD servers</a></li>
- <li><a href="#conclusion" data-toggle="tab">Conclusion</a></li>
- </ul>
-
- <div class="tab-content">
- <div class="tab-pane fade in active" id="introduction">
- <h3>Introduction</h3>
- <p>You are now root inside a LXD container with a
- nested LXD installed inside it.
- </p>
-
- <p>Initial startup can take a few seconds due to
- having to generate SSL keys on a rather busy system.
- <br />
- Further commands should then be near instantaneous.
- </p>
-
- <p>You're welcome to just poke around and
- discover LXD through its manpage and --help
- option.
- <br />
- Or you can follow this step by step tutorial
- instead which will get you through LXD's
- main features.
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="disabled"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
-
- <div class="tab-pane fade in" id="first-container">
- <h3>Your first container</h3>
-
- <p>LXD is image based, however by default no
- images are loaded into the image store as can
- be seen with: <pre>lxc image list</pre>
- </p>
-
- <p>LXD knows about 3 default image servers:
- <ul>
- <li>ubuntu: (for Ubuntu stable images)</li>
- <li>ubuntu-daily: (for Ubuntu daily images)</li>
- <li>images: (for a bunch of other distributions)</li>
- </ul>
- </p>
-
- <p>The stable Ubuntu images can be listed with:
- <pre>lxc image list ubuntu: | less</pre>
- </p>
-
- <p>To launch a first container called "first"
- using the Ubuntu 16.04 image, use:
- <pre>lxc launch ubuntu:16.04 first</pre>
- </p>
-
- <p>Your new container will now be visible in:
- <pre>lxc list</pre>
- </p>
-
- <p>Running state details and configuration can
- be queried with:
- <pre>lxc info first
-lxc config show first</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
-
- <div class="tab-pane fade in" id="limiting-resources">
- <h3>Limiting resources</h3>
-
- <p>By default your container comes with no
- resource limitation and inherits from its
- parent environment. You can confirm it with:
- <pre>free -m
-lxc exec first -- free -m</pre>
- </p>
-
- <p>To apply a memory limit to your container, do:
- <pre>lxc config set first limits.memory 128MB</pre>
- </p>
+ <div class="panel panel-success" id="tryit_status_panel" style="display:none">
+ <div class="panel-heading">Server status</div>
+ <div class="panel-body" id="tryit_online_message" style="display:none">
+ You are connected over: <span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
+ The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span>
+ </div>
- <p>And confirm that it's been applied with:
- <pre>lxc exec first -- free -m</pre>
- </p>
+ <div class="panel-body" id="tryit_maintenance_message" style="display:none">
+ The demo service is currently down for maintenance and should be
+ back online in a few minutes.
+ </div>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
+ <div class="panel-body" id="tryit_unreachable_message" style="display:none">
+ Your browser couldn't reach the demo server.<br />
+ This is either (most likely) because of a firewall or proxy
+ issue on your side or because of a network, power or other catastrophic
+ server side failure.
+ </div>
</div>
- <div class="tab-pane fade in" id="snapshots">
- <h3>Snapshots</h3>
-
- <p>LXD supports snapshoting and restoring
- container snapshots.
- <br />
- Before making a snapshot, lets do some
- changes to the container, for example, updating it:
- <pre>lxc exec first -- apt-get update
-lxc exec first -- apt-get dist-upgrade -y
-lxc exec first -- apt-get autoremove --purge -y</pre>
- </p>
-
- <p>Now that the container is all updated and
- cleaned, let's make a snapshot called "clean":
- <pre>lxc snapshot first clean</pre>
- </p>
-
- <p>Let's break our container:
- <pre>lxc exec first -- rm -Rf /etc /usr</pre>
- </p>
-
- <p>Confirm the breakage with (then exit):
- <pre>lxc exec first -- bash</pre>
- </p>
-
- <p>And restore everything to the snapshotted state:
- <pre>lxc restore first clean</pre>
- </p>
-
- <p>And confirm everything's back to normal (then exit):
- <pre>lxc exec first -- bash</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
+ <div class="panel panel-primary" id="tryit_terms_panel" style="display:none">
+ <div class="panel-heading">Terms of service</div>
+ <div class="panel-body" id="tryit_terms"></div>
</div>
- <div class="tab-pane fade in" id="creating-images">
- <h3>Creating images</h3>
-
- <p>As your probably noticed earlier, LXD is
- image based, that is, all containers must be
- created from either a copy of an existing
- container or from an image.</p>
-
- <p>You can create new images from an existing
- container or a container snapshot.</p>
-
- <p>To publish our "clean" snapshot from earlier
- as a new image with a user friendly alias of
- "clean-ubuntu", run:
- <pre>lxc publish first/clean --alias clean-ubuntu</pre>
- </p>
-
- <p>At which point we won't need our "first"
- container, so just delete it with:
- <pre>lxc stop first
-lxc delete first</pre>
- </p>
-
- <p>And lastly we can start a new container from
- our image with:
- <pre>lxc launch clean-ubuntu second</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
+ <div class="panel panel-warning" id="tryit_start_panel" style="display:none">
+ <div class="panel-heading">Start</div>
+ <div class="panel-body">
+ <button class="btn btn-default btn-lg" id="tryit_accept" type="button">
+ <span aria-hidden="true" class="glyphicon glyphicon-ok"></span>
+ I have read and accept the terms of service above
+ </button>
+
+ <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
+ <p>
+ <big>Starting the container...</big>
+ </p>
+ <p>
+ <div class="large spinner"></div>
+ </p>
+ </div>
+ </div>
</div>
- <div class="tab-pane fade in" id="container-files">
- <h3>Accessing files from the container</h3>
-
- <p>To pull a file from the container you can use
- the "lxc file pull" command:
- <pre>lxc file pull second/etc/hosts .</pre>
- </p>
-
- <p>Let's add an entry to it:
- <pre>echo "1.2.3.4 my-example" >> hosts</pre>
- </p>
-
- <p>And push it back where it came from:
- <pre>lxc file push hosts second/etc/hosts</pre>
- </p>
-
- <p>You can also use this mechanism to access log files:
- <pre>lxc file pull second/var/log/syslog - | less</pre>
- </p>
-
- <p>We won't be needing that container anymore,
- so stop and delete it with:
- <pre>lxc delete --force second</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
+ <div class="panel panel-success" id="tryit_info_panel" style="display:none">
+ <div class="panel-heading">Container information</div>
+ <table class="table" style="padding-left: 15px;">
+ <tr id="tryit_lxd_row">
+ <th>Remote LXD</th>
+ <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
+ </tr>
+
+ <tr id="tryit_clock">
+ <th>Remaining time</th>
+ <td><span class="minutes"></span> minutes, <span class="seconds"></span> seconds</td>
+ </tr>
+ </table>
</div>
- <div class="tab-pane fade in" id="image-server">
- <h3>Use a remote image server</h3>
-
- <p>The lxc client tool supports multiple
- "remotes", those remotes can be read-only
- image servers or other LXD hosts.</p>
-
- <p>LXC upstream runs one such server at
- <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
- which serves a set of automatically generated
- images for various Linux distributions.
- </p>
-
- <p>It comes pre-added with default LXD but you
- can remove it or change it if you don't want it.
- </p>
-
- <p>You can list the available images with:
- <pre>lxc image list images: | less</pre>
- </p>
-
- <p>And spawn a new Centos 7 container with:
- <pre>lxc launch images:centos/7 third</pre>
- </p>
-
- <p>Confirm it's indeed Centos 7 with:
- <pre>lxc exec third -- cat /etc/redhat-release</pre>
- </p>
-
- <p>And delete it:
- <pre>lxc delete -f third</pre>
- </p>
+ <div class="panel panel-primary" id="tryit_console_panel" style="display:none">
+ <div class="panel-heading">Terminal</div>
+ <div id="tryit_console" style="background-color:black;"></div>
- <p>The list of all configured remotes can be
- obtained with:
- <pre>lxc remote list</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
+ <button class="btn btn-default btn-lg" id="tryit_console_reconnect" type="button" style="display:none">
+ <span aria-hidden="true" class="glyphicon glyphicon-repeat"></span>
+ Reconnect
+ </button>
</div>
- <div class="tab-pane fade in" id="remote-lxd">
- <h3>Interact with remote LXD servers</h3>
-
- <p>For this step, you'll need a second demo
- session, so open a new one
- <a href="/lxd/try-it/" target="_blank">here</a></p>
-
- <p>Copy/paste the "lxc remote add" command from
- the top of the page of that new session into
- the shell of your old session.
- <br />
- Then confirm the server fingerprint for the remote
- server.</p>
-
- <p>Note that it may take a few seconds for the
- new LXD daemon to listen to the network, just
- retry the command until it answers.</p>
-
- <p>At this point you can list the remote
- containers with: <pre>lxc list tryit:</pre></p>
-
- <p>And its images with:
- <pre>lxc image list tryit:</pre>
- </p>
-
- <p>Now, let's start a new container on the remote
- LXD using the local image we created earlier.
- <pre>lxc launch clean-ubuntu tryit:fourth</pre>
- </p>
-
- <p>You now have a container called "fourth"
- running on the remote host "tryit". You can
- spawn a shell inside it with (then exit):
- <pre>lxc exec tryit:fourth bash</pre>
- </p>
-
- <p>Now let's copy that container into a new one
- called "fifth":
- <pre>lxc copy tryit:fourth tryit:fifth</pre>
- </p>
-
- <p>And just for fun, move it back to our local
- lxd while renaming it to "sixth":
- <pre>lxc move tryit:fifth sixth</pre>
- </p>
-
- <p>And confirm it's all still working (then exit):
- <pre>lxc start sixth
-lxc exec sixth -- bash</pre>
- </p>
-
- <p>Then clean everything up:
- <pre>lxc delete -f sixth
-lxc delete -f tryit:fourth
-lxc image delete clean-ubuntu</pre>
- </p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
+ <div class="panel panel-warning" id="tryit_examples_panel" style="display:none">
+ <div class="panel-heading"><a data-toggle="collapse" class="text" href="#tryit_examples_collapse">Step by step instructions</a></div>
+ <div class="panel-body collapse in" id="tryit_examples_collapse">
+ <ul class="nav nav-tabs" style="display:none">
+ <li class="active"><a href="#introduction" data-toggle="tab">Introduction</a></li>
+ <li><a href="#first-container" data-toggle="tab">Your first container</a></li>
+ <li><a href="#limiting-resources" data-toggle="tab">Limiting resources</a></li>
+ <li><a href="#snapshots" data-toggle="tab">Snapshots</a></li>
+ <li><a href="#creating-images" data-toggle="tab">Creating images</a></li>
+ <li><a href="#container-files" data-toggle="tab">Accessing files from the container</a></li>
+ <li><a href="#image-server" data-toggle="tab">Use a remote image server</a></li>
+ <li><a href="#remote-lxd" data-toggle="tab">Interact with remote LXD servers</a></li>
+ <li><a href="#conclusion" data-toggle="tab">Conclusion</a></li>
</ul>
- </nav>
- </div>
-
-
- <div class="tab-pane fade in" id="conclusion">
- <h3>Conclusion</h3>
-
- <p>We hope this gave you a good introduction to
- LXD, its capabilities and how easy it is to
- use.</p>
- <p>You're welcome to use the demo service as
- long as you want to try LXD and play with the
- latest features.</p>
-
- <p>Enjoy!</p>
-
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="disabled"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
- </div>
- </div>
-</div>
-
-<div class="panel panel-primary" id="tryit_feedback" style="display:none">
- <div class="panel-heading"><a data-toggle="collapse" class="text" href="#tryit_feedback_collapse">Feedback</a></div>
- <div class="panel-body collapse in" id="tryit_feedback_collapse">
- <form id="tryit_feedback_submit">
- <div class="form-group">
- <label for="feedbackRating">Rate your experience</label>
- <br />
- <input type="hidden" class="rating rating-tooltip" id="feedbackRating" />
- </div>
-
- <div class="form-group">
- <label for="feedbackEmail">Email address (optional)</label>
- <input type="email" class="form-control" id="feedbackEmail" placeholder="foo at bar.com"/>
- <small id="feedbackEmailHelp" class="form-text text-muted">Fill this to allow us to contact you about your feedback.</small>
-
- <div class="form-check">
- <label class="form-check-label">
- <input type="checkbox" class="form-check-input" id="feedbackEmailUse"/>
- I'm interested in hearing more about LXD and related products from Canonical.
- </label>
+ <div class="tab-content">
+ <div class="tab-pane fade in active" id="introduction">
+ <h3>Introduction</h3>
+ <p>You are now root inside a LXD container with a
+ nested LXD installed inside it.
+ </p>
+
+ <p>Initial startup can take a few seconds due to
+ having to generate SSL keys on a rather busy system.
+ <br />
+ Further commands should then be near instantaneous.
+ </p>
+
+ <p>You're welcome to just poke around and
+ discover LXD through its manpage and --help
+ option.
+ <br />
+ Or you can follow this step by step tutorial
+ instead which will get you through LXD's
+ main features.
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="disabled"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="first-container">
+ <h3>Your first container</h3>
+
+ <p>LXD is image based, however by default no
+ images are loaded into the image store as can
+ be seen with: <pre>lxc image list</pre>
+ </p>
+
+ <p>LXD knows about 3 default image servers:
+ <ul>
+ <li>ubuntu: (for Ubuntu stable images)</li>
+ <li>ubuntu-daily: (for Ubuntu daily images)</li>
+ <li>images: (for a bunch of other distributions)</li>
+ </ul>
+ </p>
+
+ <p>The stable Ubuntu images can be listed with:
+ <pre>lxc image list ubuntu: | less</pre>
+ </p>
+
+ <p>To launch a first container called "first"
+ using the Ubuntu 16.04 image, use:
+ <pre>lxc launch ubuntu:16.04 first</pre>
+ </p>
+
+ <p>Your new container will now be visible in:
+ <pre>lxc list</pre>
+ </p>
+
+ <p>Running state details and configuration can
+ be queried with:
+ <pre>lxc info first
+ lxc config show first</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="limiting-resources">
+ <h3>Limiting resources</h3>
+
+ <p>By default your container comes with no
+ resource limitation and inherits from its
+ parent environment. You can confirm it with:
+ <pre>free -m
+ lxc exec first -- free -m</pre>
+ </p>
+
+ <p>To apply a memory limit to your container, do:
+ <pre>lxc config set first limits.memory 128MB</pre>
+ </p>
+
+ <p>And confirm that it's been applied with:
+ <pre>lxc exec first -- free -m</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="snapshots">
+ <h3>Snapshots</h3>
+
+ <p>LXD supports snapshoting and restoring
+ container snapshots.
+ <br />
+ Before making a snapshot, lets do some
+ changes to the container, for example, updating it:
+ <pre>lxc exec first -- apt-get update
+ lxc exec first -- apt-get dist-upgrade -y
+ lxc exec first -- apt-get autoremove --purge -y</pre>
+ </p>
+
+ <p>Now that the container is all updated and
+ cleaned, let's make a snapshot called "clean":
+ <pre>lxc snapshot first clean</pre>
+ </p>
+
+ <p>Let's break our container:
+ <pre>lxc exec first -- rm -Rf /etc /usr</pre>
+ </p>
+
+ <p>Confirm the breakage with (then exit):
+ <pre>lxc exec first -- bash</pre>
+ </p>
+
+ <p>And restore everything to the snapshotted state:
+ <pre>lxc restore first clean</pre>
+ </p>
+
+ <p>And confirm everything's back to normal (then exit):
+ <pre>lxc exec first -- bash</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="creating-images">
+ <h3>Creating images</h3>
+
+ <p>As your probably noticed earlier, LXD is
+ image based, that is, all containers must be
+ created from either a copy of an existing
+ container or from an image.</p>
+
+ <p>You can create new images from an existing
+ container or a container snapshot.</p>
+
+ <p>To publish our "clean" snapshot from earlier
+ as a new image with a user friendly alias of
+ "clean-ubuntu", run:
+ <pre>lxc publish first/clean --alias clean-ubuntu</pre>
+ </p>
+
+ <p>At which point we won't need our "first"
+ container, so just delete it with:
+ <pre>lxc stop first
+ lxc delete first</pre>
+ </p>
+
+ <p>And lastly we can start a new container from
+ our image with:
+ <pre>lxc launch clean-ubuntu second</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="container-files">
+ <h3>Accessing files from the container</h3>
+
+ <p>To pull a file from the container you can use
+ the "lxc file pull" command:
+ <pre>lxc file pull second/etc/hosts .</pre>
+ </p>
+
+ <p>Let's add an entry to it:
+ <pre>echo "1.2.3.4 my-example" >> hosts</pre>
+ </p>
+
+ <p>And push it back where it came from:
+ <pre>lxc file push hosts second/etc/hosts</pre>
+ </p>
+
+ <p>You can also use this mechanism to access log files:
+ <pre>lxc file pull second/var/log/syslog - | less</pre>
+ </p>
+
+ <p>We won't be needing that container anymore,
+ so stop and delete it with:
+ <pre>lxc delete --force second</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="image-server">
+ <h3>Use a remote image server</h3>
+
+ <p>The lxc client tool supports multiple
+ "remotes", those remotes can be read-only
+ image servers or other LXD hosts.</p>
+
+ <p>LXC upstream runs one such server at
+ <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
+ which serves a set of automatically generated
+ images for various Linux distributions.
+ </p>
+
+ <p>It comes pre-added with default LXD but you
+ can remove it or change it if you don't want it.
+ </p>
+
+ <p>You can list the available images with:
+ <pre>lxc image list images: | less</pre>
+ </p>
+
+ <p>And spawn a new Centos 7 container with:
+ <pre>lxc launch images:centos/7 third</pre>
+ </p>
+
+ <p>Confirm it's indeed Centos 7 with:
+ <pre>lxc exec third -- cat /etc/redhat-release</pre>
+ </p>
+
+ <p>And delete it:
+ <pre>lxc delete -f third</pre>
+ </p>
+
+ <p>The list of all configured remotes can be
+ obtained with:
+ <pre>lxc remote list</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+ <div class="tab-pane fade in" id="remote-lxd">
+ <h3>Interact with remote LXD servers</h3>
+
+ <p>For this step, you'll need a second demo
+ session, so open a new one
+ <a href="/lxd/try-it/" target="_blank">here</a></p>
+
+ <p>Copy/paste the "lxc remote add" command from
+ the top of the page of that new session into
+ the shell of your old session.
+ <br />
+ Then confirm the server fingerprint for the remote
+ server.</p>
+
+ <p>Note that it may take a few seconds for the
+ new LXD daemon to listen to the network, just
+ retry the command until it answers.</p>
+
+ <p>At this point you can list the remote
+ containers with: <pre>lxc list tryit:</pre></p>
+
+ <p>And its images with:
+ <pre>lxc image list tryit:</pre>
+ </p>
+
+ <p>Now, let's start a new container on the remote
+ LXD using the local image we created earlier.
+ <pre>lxc launch clean-ubuntu tryit:fourth</pre>
+ </p>
+
+ <p>You now have a container called "fourth"
+ running on the remote host "tryit". You can
+ spawn a shell inside it with (then exit):
+ <pre>lxc exec tryit:fourth bash</pre>
+ </p>
+
+ <p>Now let's copy that container into a new one
+ called "fifth":
+ <pre>lxc copy tryit:fourth tryit:fifth</pre>
+ </p>
+
+ <p>And just for fun, move it back to our local
+ lxd while renaming it to "sixth":
+ <pre>lxc move tryit:fifth sixth</pre>
+ </p>
+
+ <p>And confirm it's all still working (then exit):
+ <pre>lxc start sixth
+ lxc exec sixth -- bash</pre>
+ </p>
+
+ <p>Then clean everything up:
+ <pre>lxc delete -f sixth
+ lxc delete -f tryit:fourth
+ lxc image delete clean-ubuntu</pre>
+ </p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="active"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+
+
+ <div class="tab-pane fade in" id="conclusion">
+ <h3>Conclusion</h3>
+
+ <p>We hope this gave you a good introduction to
+ LXD, its capabilities and how easy it is to
+ use.</p>
+
+ <p>You're welcome to use the demo service as
+ long as you want to try LXD and play with the
+ latest features.</p>
+
+ <p>Enjoy!</p>
+
+ <nav aria-label="...">
+ <ul class="pager">
+ <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
+ <li class="disabled"><a href="#" class="tabNext">Next</a></li>
+ </ul>
+ </nav>
+ </div>
+ </div>
</div>
</div>
- <div class="form-group">
- <label for="feedbackText">Feedback (optional)</label>
- <textarea class="form-control" id="feedbackText" rows="5"></textarea>
+ <div class="p-notification--information" id="tryit_feedback" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status"><a data-toggle="collapse" class="text" href="#tryit_feedback_collapse">Feedback</a></span>
+ <div class="panel-body collapse in" id="tryit_feedback_collapse">
+ <form class="p-form" id="tryit_feedback_submit">
+ <div class="p-form__group">
+ <label for="feedbackRating">Rate your experience</label>
+ <br />
+ <input type="hidden" class="rating rating-tooltip" id="feedbackRating" />
+ </div>
+
+ <div class="p-form__group">
+ <label for="feedbackEmail">Email address (optional)</label>
+ <input type="email" class="form-control" id="feedbackEmail" placeholder="foo at bar.com"/>
+ <small id="feedbackEmailHelp" class="form-text text-muted">Fill this to allow us to contact you about your feedback.</small>
+
+ <div class="form-check">
+ <label class="form-check-label">
+ <input type="checkbox" class="form-check-input" id="feedbackEmailUse"/>
+ I'm interested in hearing more about LXD and related products from Canonical.
+ </label>
+ </div>
+ </div>
+
+ <div class="p-form__group">
+ <label for="feedbackText">Feedback (optional)</label>
+ <textarea class="form-control" id="feedbackText" rows="5"></textarea>
+ </div>
+
+ <button type="submit" class="p-button--positive">Send feedback</button>
+ </form>
+ </div>
+ </div>
</div>
- <button type="submit" class="btn btn-primary">Send feedback</button>
- </form>
- </div>
-</div>
+ <div class="panel panel-danger" id="tryit_error_panel" style="display:none">
+ <div class="panel-heading" id="tryit_error_panel_create" style="display:none">Unable to create a new container</div>
+ <div class="panel-heading" id="tryit_error_panel_access" style="display:none">Unable to access the container</div>
-<div class="panel panel-danger" id="tryit_error_panel" style="display:none">
- <div class="panel-heading" id="tryit_error_panel_create" style="display:none">Unable to create a new container</div>
- <div class="panel-heading" id="tryit_error_panel_access" style="display:none">Unable to access the container</div>
+ <div class="panel-body" id="tryit_error_full" style="display:none">
+ The server is currently full, please try again in a few minutes.
- <div class="panel-body" id="tryit_error_full" style="display:none">
- The server is currently full, please try again in a few minutes.
+ <br /><br />
- <br /><br />
-
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
+ <button class="btn btn-default btn-lg tryit_goback" type="button">
+ <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
+ Start over
+ </button>
+ </div>
- <div class="panel-body" id="tryit_error_quota" style="display:none">
- You have reached the maximum number of concurrent sessions,
- please wait for some to expire before starting more of them.
+ <div class="panel-body" id="tryit_error_quota" style="display:none">
+ You have reached the maximum number of concurrent sessions,
+ please wait for some to expire before starting more of them.
- <br /><br />
+ <br /><br />
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
+ <button class="btn btn-default btn-lg tryit_goback" type="button">
+ <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
+ Start over
+ </button>
+ </div>
- <div class="panel-body" id="tryit_error_banned" style="display:none">
- You have been banned from this service due to a failure to
- respect the terms of service.
- </div>
+ <div class="panel-body" id="tryit_error_banned" style="display:none">
+ You have been banned from this service due to a failure to
+ respect the terms of service.
+ </div>
- <div class="panel-body" id="tryit_error_unknown" style="display:none">
- An unknown error occured. Please try again in a few minutes.
+ <div class="panel-body" id="tryit_error_unknown" style="display:none">
+ An unknown error occured. Please try again in a few minutes.
- <br /><br />
+ <br /><br />
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
+ <button class="btn btn-default btn-lg tryit_goback" type="button">
+ <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
+ Start over
+ </button>
+ </div>
- <div class="panel-body" id="tryit_error_missing" style="display:none">
- The container you're trying to connect to doesn't exist anymore.
+ <div class="panel-body" id="tryit_error_missing" style="display:none">
+ The container you're trying to connect to doesn't exist anymore.
- <br /><br />
+ <br /><br />
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
+ <button class="btn btn-default btn-lg tryit_goback" type="button">
+ <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
+ Start over
+ </button>
+ </div>
+ </div>
+ </div>
</div>
</div>
diff --git a/generate b/generate
index 658662b..7412eed 100755
--- a/generate
+++ b/generate
@@ -222,6 +222,7 @@ def gen_page(entry, override, prefix, **variables):
with open(content_path(item['meta']['input']), "r") as fd:
content = fd.read()
elif item['generator'] == "markdown":
+ template = "markdown-page.tpl.html"
with open(content_path(item['meta']['input']), "r") as fd:
content = md2html(fd.read())
elif item['generator'] == "downloads":
diff --git a/static/css/local.css b/static/css/local.css
index ce94c92..66a717d 100644
--- a/static/css/local.css
+++ b/static/css/local.css
@@ -1,121 +1,10 @@
-#navbar-title {
- color: white;
+body {
+ padding-top: 0 !important;
}
-#breadcrumb-logo {
- height: 1em;
- display: inline;
-}
-
-a.text {
- color: inherit;
- text-decoration: inherit;
-}
-
-div.container p {
- font-size: 16px;
-}
-
-div.container pre {
- margin-left: 30px;
-}
-
-div.container p img {
- float: right;
- margin-left: auto;
- margin-right: auto;
- max-width: 30%;
- padding: 5px;
-}
-
-div.large_content p {
- font-size: 20px;
-}
-
-div.row p {
- font-size: 14px;
-}
-
-hr {
- margin-top: 40px;
- margin-bottom: 40px;
-}
-
-hr.footer {
- margin-bottom: 5px;
-}
-
-span.text-muted {
- white-space:nowrap;
-}
-
-div.codehilite pre {
- margin-left: 0;
-}
-
-div.manpage {
- max-width: 45em;
-}
-
-.dropdown-submenu {
- position:relative;
-}
-
-.dropdown-submenu>.dropdown-menu {
- top:0;
- left:100%;
- margin-top:-6px;
- margin-left:-1px;
- -webkit-border-radius:0 6px 6px 6px;
- -moz-border-radius:0 6px 6px 6px;
- border-radius:0 6px 6px 6px;
-}
-
-.dropdown-submenu:hover>.dropdown-menu {
- display:block;
-}
-
-.dropdown-submenu>a:after {
- display:block;
- content:" ";
- float:right;
- width:0;
- height:0;
- border-color:transparent;
- border-style:solid;
- border-width:5px 0 5px 5px;
- border-left-color:#cccccc;
- margin-top:5px;
- margin-right:-10px;
-}
-
-.dropdown-submenu:hover>a:after {
- border-left-color:#ffffff;
-}
-
-.dropdown-submenu.pull-left {
- float:none;
-}
-
-.dropdown-submenu.pull-left>.dropdown-menu {
- left:-100%;
- margin-left:10px;
- -webkit-border-radius:6px 0 6px 6px;
- -moz-border-radius:6px 0 6px 6px;
- border-radius:6px 0 6px 6px;
-}
-
-.tab-pane h3 {
- margin-top: 0;
-}
-
-.tab-pane nav .pager {
- margin-top: 5px;
- margin-bottom: 0;
-}
-
-.panel {
- margin-bottom: 10px;
+.hover-menu li {
+ color: #999;
+ cursor: auto;
}
/* paragraph anchors as generated by markdown toc */
@@ -130,113 +19,11 @@ h3:hover a.headerlink {
visibility:visible;
}
-
- at media screen and (max-width: 991px){
- .columns{
- height: 500px;
- overflow:scroll;
- }
-}
-
- at media screen and (min-width: 992px){
- .columns{
- -moz-column-count:2; /* Firefox */
- -webkit-column-count:2; /* Safari and Chrome */
- column-count:2;
- width: 500px;
- }
-}
-
-#tryit_console {
- display: table;
- margin: 0 auto;
- font-family: "DejaVu Sans Mono", "Liberation Mono", monospace;
- font-size: 11px;
- width: 100%;
-
- text-size-adjust: none;
- -moz-text-size-adjust: none;
- -webkit-text-size-adjust: none;
- -ms-text-size-adjust: none;
-}
-
-#tryit_console_measurement {
- color: white;
- display: block;
- float: left;
- border-color:black;
- border-style:solid;
- border-width:5px 5px 5px 5px;
- position:absolute;
- top:-1000px;
-}
-
-.tryit_run:hover {
- text-decoration: underline;
- cursor: pointer;
-}
-
-.btn {
- white-space: normal;
-}
-
- at keyframes spin {
- to { transform: rotate(1turn); }
-}
-
-.spinner {
- position: relative;
- display: inline-block;
- width: 5em;
- height: 5em;
- margin: 0 .5em;
- font-size: 12px;
- text-indent: 999em;
- overflow: hidden;
- animation: spin 1s infinite steps(8);
-}
-
-.small.spinner {
- font-size: 6px;
-}
-
-.large.spinner {
- font-size: 24px;
-}
-
-.spinner:before,
-.spinner:after,
-.spinner > div:before,
-.spinner > div:after {
- content: '';
- position: absolute;
- top: 0;
- left: 2.25em; /* (container width - part width)/2 */
- width: .5em;
- height: 1.5em;
- border-radius: .2em;
- background: #eee;
- box-shadow: 0 3.5em #eee; /* container height - part height */
- transform-origin: 50% 2.5em; /* container height / 2 */
-}
-
-.spinner:before {
- background: #555;
-}
-
-.spinner:after {
- transform: rotate(-45deg);
- background: #777;
-}
-
-.spinner > div:before {
- transform: rotate(-90deg);
- background: #999;
-}
-
-.spinner > div:after {
- transform: rotate(-135deg);
- background: #bbb;
+.divider {
+ height: 1px;
+ padding: 0;
+ margin-bottom: -10px;
+ border-top: 1px solid #999;
}
.symbol {
diff --git a/templates/common/base.tpl.html b/templates/common/base.tpl.html
index 5a8e0e4..9548492 100644
--- a/templates/common/base.tpl.html
+++ b/templates/common/base.tpl.html
@@ -12,9 +12,7 @@
<title>Linux Containers</title>
{% endif %}
- <!-- Bootstrap core CSS -->
- <link href="/static/css/bootstrap.min.css" rel="stylesheet"/>
- <link href="/static/css/bootstrap-theme.min.css" rel="stylesheet"/>
+ <link rel="stylesheet" href="https://assets.ubuntu.com/v1/vanilla-framework-version-1.6.0.min.css" />
<link href="/static/css/local.css" rel="stylesheet"/>
<link href="/static/css/pygments.css" rel="stylesheet"/>
@@ -34,16 +32,25 @@
<body role="document">
{% include "common/header.tpl.html" %}
- <div class="container">
- <ol class="breadcrumb">
- <li><img id="breadcrumb-logo" src="/static/img/containers.png"/></li>
+<div class="p-breadcrumbs nav-secondary clearfix">
+ <div class="row nav-secondary__row">
+ <div class="col-12 u-no-margin--bottom">
+ <ul class="p-breadcrumbs u-no-margin--bottom">
{% if page_menu %}
{% for entry in page_menu %}
- <li>{{ entry }}</li>
+ <li class="p-breadcrumbs__item">{{ entry }}</li>
{% endfor %}
{% endif %}
- </ol>
-{% block content %}{% endblock %}
+ </ul>
+ </div>
+ </div>
+</div>
+
+<div class="wrapper u-no-margin--top">
+ <div class="inner-wrapper" id="main-content">
+ {% block content %}{% endblock %}
+ </div>
+</div>
{% include ["common/footer." + page_language[0] + ".tpl.html", "common/footer.tpl.html"] %}
diff --git a/templates/common/footer.tpl.html b/templates/common/footer.tpl.html
index f13fd6b..302d0b5 100644
--- a/templates/common/footer.tpl.html
+++ b/templates/common/footer.tpl.html
@@ -1,9 +1,18 @@
-<hr class="footer"/>
-<footer>
- <p class="pull-left"><a href="https://github.com/lxc/linuxcontainers.org">Improve this website</a></p>
- <p class="pull-right"><a href="#">Back to top</a></p>
- <p class="text-center">
- <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Content under Creative Commons CC BY NC SA</a><br />
- <span class="small">Project sponsored by <a href="http://www.canonical.com">Canonical Ltd.</a></span>
- </p>
+<footer class="p-footer">
+ <div class="row">
+ <p>Project sponsored by <a href="http://www.canonical.com">Canonical Ltd.</a></p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">Improve this website</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">Back to top</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Content under Creative Commons CC BY NC SA</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
diff --git a/templates/common/header.tpl.html b/templates/common/header.tpl.html
index f376391..0ae4d7d 100644
--- a/templates/common/header.tpl.html
+++ b/templates/common/header.tpl.html
@@ -1,44 +1,48 @@
-<nav class="navbar navbar-inverse navbar-static-top" role="navigation">
- <div class="container">
- <div class="navbar-header">
- <span class="navbar-brand" id="navbar-title">Linux Containers</span>
+<div class="p-navigation">
+ <div class="row">
+ <div class="p-navigation__logo">
+ <a class="p-navigation__link" href="/">Linux Containers</a>
</div>
- <div id="navbar" class="navbar-collapse">
+ <nav class="p-navigation__nav">
+ <span class="u-off-screen">
+ <a href="#main-content">Jump to main content</a>
+ </span>
{% if menu %}
- <ul class="nav navbar-nav">
+ <ul class="p-navigation__links">
{% for entry in menu %}
{% if entry[0] is string %}
{% if page_path == entry[0] %}
- <li class="active"><a href="#">{{ entry[1] }}</a></li>
+ <li class="p-navigation__link is-active"><a href="#">{{ entry[1] }}</a></li>
{% else %}
- <li><a href="{{ entry[0] }}">{{ entry[1] }}</a></li>
+ <li class="p-navigation__link"><a href="{{ entry[0] }}">{{ entry[1] }}</a></li>
{% endif %}
{% else %}
{% if page_menu and page_menu[0] == entry[1] %}
- <li class="dropdown active">
+ <li class="p-navigation__link is-active">
{% else %}
- <li class="dropdown">
+ <li class="p-navigation__link">
{% endif %}
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">{{ entry[1] }} <span class="caret"></span></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">{{ entry[1] }}</a>
+
+ <ul class="hover-menu " role="menu">
- <ul class="dropdown-menu" role="menu">
{% for sub_entry in entry[0] %}
{% if not sub_entry[0] %}
- <li class="divider"></li>
+ <li class="divider"></li>
{% if sub_entry[1] %}
- <li class="dropdown-header">{{ sub_entry[1] }}</li>
+ <li>{{ sub_entry[1] }}</li>
{% endif %}
{% else %}
{% if sub_entry[0] is string %}
{% if page_path == sub_entry[0] %}
- <li class="active"><a href="#">{{ sub_entry[1] }}</a></li>
+ <li><a href="#">{{ sub_entry[1] }}</a></li>
{% else %}
<li><a href="{{ sub_entry[0] }}">{{ sub_entry[1] }}</a></li>
{% endif %}
{% else %}
{% if page_menu[1] == sub_entry[1] %}
- <li class="dropdown-submenu active">
+ <li class="is-active">
{% else %}
<li class="dropdown-submenu">
{% endif %}
@@ -51,13 +55,12 @@
{% endif %}
{% for sub_sub_entry in sub_entry[0] %}
{% if not sub_sub_entry[0] %}
- <li class="divider"></li>
{% if sub_sub_entry[1] %}
<li class="dropdown-header">{{ sub_sub_entry[1] }}</li>
{% endif %}
{% else %}
{% if page_path == sub_sub_entry[0] %}
- <li class="active"><a href="#">{{ sub_sub_entry[1] }}</a></li>
+ <li class="is-active"><a href="#">{{ sub_sub_entry[1] }}</a></li>
{% else %}
<li><a href="{{ sub_sub_entry[0] }}">{{ sub_sub_entry[1] }}</a></li>
{% endif %}
@@ -68,15 +71,15 @@
{% endif %}
{% endif %}
{% endfor %}
- </ul>
- </li>
+ </ul>
+ </li>
{% endif %}
{% endfor %}
</ul>
{% endif %}
-{% if languages %}
- <ul class="nav navbar-nav navbar-right">
+{% if not languages %}
+ <ul class="u-align--right">
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">{{ page_language[2] }} <span class="caret"></span></a>
<ul class="dropdown-menu" role="menu">
diff --git a/templates/downloads.tpl.html b/templates/downloads.tpl.html
index 138e203..408d8f2 100644
--- a/templates/downloads.tpl.html
+++ b/templates/downloads.tpl.html
@@ -1,5 +1,7 @@
{% extends "common/base.tpl.html" %}
{% block content %}
+<div class="row">
+ <div class="p-strip">
{{ content }}
{% if downloads %}
@@ -19,4 +21,6 @@
{% endfor %}
</table>
{% endif %}
+</div>
+</div>
{% endblock %}
diff --git a/templates/markdown-page.tpl.html b/templates/markdown-page.tpl.html
new file mode 100644
index 0000000..fcbee1a
--- /dev/null
+++ b/templates/markdown-page.tpl.html
@@ -0,0 +1,8 @@
+{% extends "common/base.tpl.html" %}
+{% block content %}
+<div class="row">
+ <div class="p-strip">
+ {{ content }}
+ </div>
+</div>
+{% endblock %}
From 8f3f8fa7daf5496e47e0ce6aa6544439b1be3147 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Fri, 13 Oct 2017 17:54:38 +0100
Subject: [PATCH 2/8] Fix nested navigation
---
.vscode/tags | 6 ++++++
static/css/local.css | 25 +++++++++++++++++++++++++
templates/common/base.tpl.html | 2 +-
3 files changed, 32 insertions(+), 1 deletion(-)
create mode 100644 .vscode/tags
diff --git a/.vscode/tags b/.vscode/tags
new file mode 100644
index 0000000..33ed9e8
--- /dev/null
+++ b/.vscode/tags
@@ -0,0 +1,6 @@
+!_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to lines/
+!_TAG_FILE_SORTED 1 /0=unsorted, 1=sorted, 2=foldcase/
+!_TAG_PROGRAM_AUTHOR Darren Hiebert /dhiebert at users.sourceforge.net/
+!_TAG_PROGRAM_NAME Exuberant Ctags //
+!_TAG_PROGRAM_URL http://ctags.sourceforge.net /official site/
+!_TAG_PROGRAM_VERSION 5.9~svn20110310 //
diff --git a/static/css/local.css b/static/css/local.css
index 66a717d..ac931e6 100644
--- a/static/css/local.css
+++ b/static/css/local.css
@@ -26,6 +26,7 @@ h3:hover a.headerlink {
border-top: 1px solid #999;
}
+<<<<<<< 50e47ddbf10d8e51e2cfc8a11f556aca69dd7a3a
.symbol {
display: inline-block;
border-radius: 50%;
@@ -40,4 +41,28 @@ h3:hover a.headerlink {
.symbol-filled {
background-color: black;
+=======
+.dropdown-submenu:hover .dropdown-menu {
+ display: block;
+}
+
+.dropdown-submenu .dropdown-menu {
+ display: none;
+ position: absolute;
+ left: 90%;
+ margin-top: -30px;
+ background: #f7f7f7;
+ border: 1px solid #cdcdcd;
+ border-radius: 10px;
+ box-shadow: 0 2px 2px -1px #cdcdcd;
+}
+
+ at media only screen and (min-width: 768px) {
+ .dropdown-menu::after {
+ transform: rotate(-90deg);
+ left: -48px !important;
+ width: 90px !important;
+ top: 0 !important;
+ }
+>>>>>>> Fix nested navigation
}
diff --git a/templates/common/base.tpl.html b/templates/common/base.tpl.html
index 9548492..2d10580 100644
--- a/templates/common/base.tpl.html
+++ b/templates/common/base.tpl.html
@@ -12,7 +12,7 @@
<title>Linux Containers</title>
{% endif %}
- <link rel="stylesheet" href="https://assets.ubuntu.com/v1/vanilla-framework-version-1.6.0.min.css" />
+ <link rel="stylesheet" href="https://www.ubuntu.com/static/css/styles.css" />
<link href="/static/css/local.css" rel="stylesheet"/>
<link href="/static/css/pygments.css" rel="stylesheet"/>
From 5544f92004fc43d92647259cd503850b291d3d5d Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Tue, 31 Oct 2017 00:20:13 +0000
Subject: [PATCH 3/8] Compelete the set up of Vanilla on en pages
---
content/cgmanager/downloads.fr.md | 6 +-
content/cgmanager/downloads.ja.md | 6 +-
content/cgmanager/downloads.md | 6 +-
content/cgmanager/downloads.ru.md | 6 +-
content/lxc/downloads.fr.md | 14 +-
content/lxc/downloads.ja.md | 4 +-
content/lxc/downloads.ko.md | 2 +-
content/lxc/downloads.md | 10 +-
content/lxc/downloads.ru.md | 10 +-
content/lxc/news.md | 317 ++++++-----
content/lxcfs/downloads.ja.md | 6 +-
content/lxcfs/downloads.md | 6 +-
content/lxcfs/downloads.ru.md | 4 +-
content/lxcfs/news.md | 9 +-
content/lxd/contribute.ja.md | 8 +-
content/lxd/contribute.md | 6 +-
content/lxd/contribute.ru.md | 6 +-
content/lxd/downloads.ja.md | 3 +-
content/lxd/downloads.md | 4 +-
content/lxd/downloads.ru.md | 2 +-
content/lxd/getting-started-cli.ja.md | 16 +-
content/lxd/getting-started-cli.md | 16 +-
content/lxd/getting-started-cli.ru.md | 26 +-
content/lxd/getting-started-openstack.ja.md | 10 +-
content/lxd/getting-started-openstack.md | 10 +-
content/lxd/getting-started-openstack.ru.md | 12 +-
content/lxd/introduction.ja.md | 34 +-
content/lxd/introduction.md | 34 +-
content/lxd/introduction.ru.md | 2 +-
content/lxd/news.md | 2 +-
content/lxd/rest-api.ja.md | 6 +-
content/lxd/rest-api.md | 6 +-
content/lxd/rest-api.ru.md | 6 +-
content/lxd/try-it.html | 815 +++++++++++++++-------------
generate | 1 +
static/css/local.css | 571 ++++++++++++++++++-
static/js/tryit.js | 2 +-
templates/common/base.tpl.html | 3 +-
templates/common/header.tpl.html | 6 +-
templates/downloads.tpl.html | 4 +-
templates/html.tpl.html | 4 +
templates/markdown-page.tpl.html | 4 +-
templates/page.tpl.html | 8 +-
43 files changed, 1310 insertions(+), 723 deletions(-)
create mode 100644 templates/html.tpl.html
diff --git a/content/cgmanager/downloads.fr.md b/content/cgmanager/downloads.fr.md
index b77f09f..c55d1be 100644
--- a/content/cgmanager/downloads.fr.md
+++ b/content/cgmanager/downloads.fr.md
@@ -1,7 +1,7 @@
-
+
# Paquets dans les distributions
-Ubuntu et Debian fournissent des paquets de cgmanager.
-Sur ces distributions, CGManager est typiquement installé comme dépendance de LXC
+Ubuntu et Debian fournissent des paquets de cgmanager.
+Sur ces distributions, CGManager est typiquement installé comme dépendance de LXC
ou même installé par défaut avec le système.
Pour les utilisateurs d'Ubuntu, nous avons aussi une PPA officielle:
diff --git a/content/cgmanager/downloads.ja.md b/content/cgmanager/downloads.ja.md
index e3a6f67..7e3eaf2 100644
--- a/content/cgmanager/downloads.ja.md
+++ b/content/cgmanager/downloads.ja.md
@@ -1,9 +1,9 @@
-
+
# ディストリビューションでのインストール
<!--
-At this time, both Ubuntu and Debian provide cgmanager packages.
-On those, CGManager will typically come as a dependency of LXC or even be installed by default.
+At this time, both Ubuntu and Debian provide cgmanager packages.
+On those, CGManager will typically come as a dependency of LXC or even be installed by default.
If not, just install it using your package manager.
-->
diff --git a/content/cgmanager/downloads.md b/content/cgmanager/downloads.md
index 07b1ad1..1ea6056 100644
--- a/content/cgmanager/downloads.md
+++ b/content/cgmanager/downloads.md
@@ -1,7 +1,7 @@
-
+
# Distribution packages
-At this time, both Ubuntu and Debian provide cgmanager packages.
-On those, CGManager will typically come as a dependency of LXC or even be installed by default.
+At this time, both Ubuntu and Debian provide cgmanager packages.
+On those, CGManager will typically come as a dependency of LXC or even be installed by default.
If not, just install it using your package manager.
For Ubuntu users, we have an official PPA for CGManager:
diff --git a/content/cgmanager/downloads.ru.md b/content/cgmanager/downloads.ru.md
index beedf01..578ec30 100644
--- a/content/cgmanager/downloads.ru.md
+++ b/content/cgmanager/downloads.ru.md
@@ -1,7 +1,7 @@
-
+
# Пакеты для дистрибутивов
-На данный момент, Ubuntu и Debian предоставляют пакеты cgmanager.
-Для них CGManager обычно идет как зависимость LXC или даже устанавливается по умолчанию.
+На данный момент, Ubuntu и Debian предоставляют пакеты cgmanager.
+Для них CGManager обычно идет как зависимость LXC или даже устанавливается по умолчанию.
Если нет, просто установите его используя ваш менеджер пакетов.
Для пользователей Ubuntu у нас есть официальный PPA для CGManager:
diff --git a/content/lxc/downloads.fr.md b/content/lxc/downloads.fr.md
index 204fb89..5be68e7 100644
--- a/content/lxc/downloads.fr.md
+++ b/content/lxc/downloads.fr.md
@@ -1,14 +1,14 @@
-
+
# Paquets dans les distributions
-LXC est inclus dans la majorité des distributions Linux.
-Dans la plupart des cas, il ne suffit que de le sélectionner dans
+LXC est inclus dans la majorité des distributions Linux.
+Dans la plupart des cas, il ne suffit que de le sélectionner dans
votre géstionaire de paquets pour l'installer.
-Assez souvent les distributions fournissent aussi des "backports" de versions
-plus récentes de LXC pour la version stable du système.
+Assez souvent les distributions fournissent aussi des "backports" de versions
+plus récentes de LXC pour la version stable du système.
Cela peut être une option intéressante, surtout si votre distribution n'inclus pas LXC 1.0.
-Pour un environement de production, il est recommendé de rester sur les versions 1.0.x de LXC
+Pour un environement de production, il est recommendé de rester sur les versions 1.0.x de LXC
car elles sont suppportées plus longtemps (jusqu'à avril 2019).
Pour les utilisateurs d'Ubuntu, nous avons aussi des PPAs officielles:
@@ -35,5 +35,5 @@ Ces branches sont clonables avec:
# Tarballs des versions stables
-Des tarballs (.tar.gz) des versions stables sont disponibles ci-dessous.
+Des tarballs (.tar.gz) des versions stables sont disponibles ci-dessous.
Toutes les versions à partir de 1.0 sont signées avec GPG par un des mainteneurs.
diff --git a/content/lxc/downloads.ja.md b/content/lxc/downloads.ja.md
index c3ec2bc..5af0a87 100644
--- a/content/lxc/downloads.ja.md
+++ b/content/lxc/downloads.ja.md
@@ -1,4 +1,4 @@
-
+
# ディストリビューションでのインストール <!-- Distribution packages -->
<!--
@@ -16,7 +16,7 @@ You may want to look for that, especially if your distribution doesn't include L
LXC 1.0 や 2.0 がディストリビューションの stable リリースに含まれない場合は特に、それを使うことも選択肢の一つでしょう。
<!--
-For production environment, try to stick to LXC 1.0.x or 2.0.x as these are the long term,
+For production environment, try to stick to LXC 1.0.x or 2.0.x as these are the long term,
stable releases which we will support until April 2019 (1.0.x) or April 2021 (2.0.x).
-->
Production 環境では、長期サポート版の stable リリースである LXC 1.0.x もしくは 2.0.x を使い続けることをお勧めします。1.0.x は 2019 年 4 月まで、2.0.x は 2021 年 4 月までサポートします。
diff --git a/content/lxc/downloads.ko.md b/content/lxc/downloads.ko.md
index db0f820..4afe437 100644
--- a/content/lxc/downloads.ko.md
+++ b/content/lxc/downloads.ko.md
@@ -1,4 +1,4 @@
-
+
# 배포판 패키지
LXC는 대부분의 리눅스 배포판에 포함이 되어 있습니다.
설치하려면 패키지 관리자에서 LXC를 선택하기만 하면 됩니다.
diff --git a/content/lxc/downloads.md b/content/lxc/downloads.md
index 9ba7acc..cd1949f 100644
--- a/content/lxc/downloads.md
+++ b/content/lxc/downloads.md
@@ -1,12 +1,12 @@
-
+
# Distribution packages
-LXC is included in most Linux distributions.
+LXC is included in most Linux distributions.
In most cases installing it is as simple as selecting it in your package manager.
-Distributions also often provide backports of newer versions of LXC for their stable releases.
+Distributions also often provide backports of newer versions of LXC for their stable releases.
You may want to look for that, especially if your distribution doesn't include LXC 1.0 or 2.0.
-For production environment, try to stick to LXC 1.0.x or 2.0.x as these are the long term,
+For production environment, try to stick to LXC 1.0.x or 2.0.x as these are the long term,
stable releases which we will support until April 2019 (1.0.x) or April 2021 (2.0.x).
For Ubuntu users, we have official PPAs for LXC:
@@ -34,5 +34,5 @@ You can clone those directly with:
# Release tarballs
-Stable release tarballs are available for download below.
+Stable release tarballs are available for download below.
All the post 1.0 ones are GPG signed by one of the maintainers.
diff --git a/content/lxc/downloads.ru.md b/content/lxc/downloads.ru.md
index adb0906..bc79354 100644
--- a/content/lxc/downloads.ru.md
+++ b/content/lxc/downloads.ru.md
@@ -1,12 +1,12 @@
-
+
# Пакеты для дистрибутивов
-LXC включен во многие дистрибутивы Linux.
+LXC включен во многие дистрибутивы Linux.
В большинстве случаев установка просто выбор его в вашем пакетном менеджере.
-Дистрибутивы часто предоставляют backports новых версий LXC для своих стабильных выпусков.
+Дистрибутивы часто предоставляют backports новых версий LXC для своих стабильных выпусков.
Вы можете захотеть взглянуть на них, особенно если ваш дистрибутив не включает LXC 1.0.
-Для окружения в продакшене остановитесь на LXC 1.0.x так как это версия с продленной поддержкой,
+Для окружения в продакшене остановитесь на LXC 1.0.x так как это версия с продленной поддержкой,
стабильный релиз который мы поддерживаем до апреля 2019.
Для пользователей Ubuntu у нас есть официальные PPAs для LXC:
@@ -33,5 +33,5 @@ LXC имеет две активных ветки git:
# Архивы TAR релизов
-Архивы TAR стабильных релизов доступны для загрузки ниже.
+Архивы TAR стабильных релизов доступны для загрузки ниже.
Начиная с 1.0 все подписаны GPG одним из ментейнеров.
diff --git a/content/lxc/news.md b/content/lxc/news.md
index 6b9972f..264d8ad 100644
--- a/content/lxc/news.md
+++ b/content/lxc/news.md
@@ -1,4 +1,3 @@
-
# News
## LXC 2.0.9 release announcement <span class="text-muted">19th of October 2017</span>
This is the nineth bugfix release for LXC 2.0.
@@ -429,17 +428,17 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.1).
## LXC 2.1 release announcement <span class="text-muted">5th of September 2017</span>
-The LXC team is proud to announce the release of LXC 2.1.
+The LXC team is proud to announce the release of LXC 2.1.
This release contains a lot of new features introduced since the release of LXC 2.0.
-Note that this isn't a LTS release and we'll therefore only be supporting LXC 2.1 for a year.
+Note that this isn't a LTS release and we'll therefore only be supporting LXC 2.1 for a year.
Production environments that require longer term support should remain on LXC 2.0 which is supported until June 2021.
## New features
### Resource limit support
-Similar to requesting specific cgroup limits users can specify any limits for any resource
-the underlying kernel is aware of by prefixing the name of the limit with "lxc.prlimit."
-in the container's configuration file. For example, to request a limit on the number of processes
+Similar to requesting specific cgroup limits users can specify any limits for any resource
+the underlying kernel is aware of by prefixing the name of the limit with "lxc.prlimit."
+in the container's configuration file. For example, to request a limit on the number of processes
and a specific nice value the configuration file for the container should contain the entries:
lxc.prlimit.nproc = unlimited
@@ -453,20 +452,20 @@ It is now possible to define openvswitch networks as an unprivileged user:
lxc.net.0.flags = up
lxc.net.0.name = eth0
-LXC 2.1. will take care to properly delete the host-side veth device from the
+LXC 2.1. will take care to properly delete the host-side veth device from the
openvswitch database on shutdown.
### New `lxc.cgroup.dir` key
-The `lxc.cgroup.dir` key lets users specify the name of the parent cgroup under
-which the container's cgroup will be created. Setting `lxc.cgroup.dir` will
+The `lxc.cgroup.dir` key lets users specify the name of the parent cgroup under
+which the container's cgroup will be created. Setting `lxc.cgroup.dir` will
override the system-wide setting for `lxc.cgroup.pattern`.
-For example, setting `lxc.cgroup.dir = mycontainers` for a container with `lxc.uts.name = c1`
+For example, setting `lxc.cgroup.dir = mycontainers` for a container with `lxc.uts.name = c1`
will cause LXC to create the cgroups `mycontainers/c1` for all controllers in the cgroup hierarchy.
### Support for hybrid cgroup layout
-Since the advent of cgroup v2 some init systems have decided to allow for a hybrid mode in which
-cgroup v1 per-controller hierarchies can be used simultaneously with an empty cgroup v2 hierarchy.
+Since the advent of cgroup v2 some init systems have decided to allow for a hybrid mode in which
+cgroup v1 per-controller hierarchies can be used simultaneously with an empty cgroup v2 hierarchy.
Systems that use this hybrid mode usually have a cgroup layout similar to this one:
/sys/fs/cgroup/blkio
@@ -474,18 +473,18 @@ Systems that use this hybrid mode usually have a cgroup layout similar to this o
/sys/fs/cgroup/memory
/sys/fs/cgroup/unified
-Where the mountpoint `/sys/fs/cgroup/unified` usually indicates the presence of a cgroup v2 hierarchy.
-This can be confirmed by testing whether `findmnt | grep cgroup2` returns a matching line.
+Where the mountpoint `/sys/fs/cgroup/unified` usually indicates the presence of a cgroup v2 hierarchy.
+This can be confirmed by testing whether `findmnt | grep cgroup2` returns a matching line.
LXC 2.1 supports this hybrid mode.
### Limiting the number of ptys a container can allocate
-Setting `lxc.pty.max` will cause LXC to mount the container's devpts with the requested limit
-on the number of useable ptys. For example, setting `lxc.pty.max = 10` will only allow
+Setting `lxc.pty.max` will cause LXC to mount the container's devpts with the requested limit
+on the number of useable ptys. For example, setting `lxc.pty.max = 10` will only allow
the container to allocate `10` ptys. The default setting is `1024`.
### `bool lxc_config_item_is_supported(const char *key)` API extension
-This function let's users query the liblxc whether a specific configuration item is supported for this library.
-This is particularly useful for embedded users that running versions of liblxc that come with significantly
+This function let's users query the liblxc whether a specific configuration item is supported for this library.
+This is particularly useful for embedded users that running versions of liblxc that come with significantly
less configuration options than the standard liblxc library or liblxc's that have backported new configuration items.
### New log API extension
@@ -514,21 +513,21 @@ less configuration options than the standard liblxc library or liblxc's that hav
These types and functions let users initialize LXC logging. This is useful for users who use the liblxc API directly.
### Deprecation of `lxc-monitord`
-Starting with LXC 2.1 the `lxc-monitord` binary is marked as deprecated.
-It is not required anymore to start daemonized containers. Instead, LXC 2.1 switches to an implementation using
-an abstract unix domain socketpair. This has the advantage of spawning one less processes on container startup which is
+Starting with LXC 2.1 the `lxc-monitord` binary is marked as deprecated.
+It is not required anymore to start daemonized containers. Instead, LXC 2.1 switches to an implementation using
+an abstract unix domain socketpair. This has the advantage of spawning one less processes on container startup which is
important for highly threaded users such as `LXD`.
Also, testing the new implementation on heavy workloads has shown this solution to be more robust and reliable in every way.
### `lxc-copy` create snapshots on `tmpfs`
-Place an ephemeral container started with -e flag on a tmpfs.
-Restrictions are that you cannot request the data to be kept while placing the container on a tmpfs,
-that either overlay or aufs backing storage must be used, and that the storage backend of the original
+Place an ephemeral container started with -e flag on a tmpfs.
+Restrictions are that you cannot request the data to be kept while placing the container on a tmpfs,
+that either overlay or aufs backing storage must be used, and that the storage backend of the original
container must be a directory.
-For ephemeral snapshots backed by overlay or aufs filesystems, a fresh tmpfs is mounted over the containers directory
-if the user requests it. This should be the easiest options. Anything else would require us to change the current
+For ephemeral snapshots backed by overlay or aufs filesystems, a fresh tmpfs is mounted over the containers directory
+if the user requests it. This should be the easiest options. Anything else would require us to change the current
mount-layout of overlay and aufs snapshots. A standard overlay or aufs snapshot clone currently has the layout:
/var/lib/lxc/CLONE_SNAPSHOT/delta0 <-- upperdir
@@ -540,26 +539,26 @@ mount-layout of overlay and aufs snapshots. A standard overlay or aufs snapshot
/var/lib/lxc/CLONE_PARENT/rootfs
-The fact that upperdir and workdir are not placed in a common subfolder under the container directory
-has the consequence that we cannot simply mount a fresh tmpfs under upperdir and workdir
+The fact that upperdir and workdir are not placed in a common subfolder under the container directory
+has the consequence that we cannot simply mount a fresh tmpfs under upperdir and workdir
because overlay expects them to be on the same filesystem.
-Because we mount a fresh tmpfs over the directory of the container the updated /etc/hostname file created
+Because we mount a fresh tmpfs over the directory of the container the updated /etc/hostname file created
during the clone residing in the upperdir (currently named "delta0" by default) will be hidden.
-Hence, if the user requests that the old name is not to be kept for the clone, we recreate this file on the tmpfs.
-This should be all that is required to restore the exact behaviour we would get with a normal clone.
+Hence, if the user requests that the old name is not to be kept for the clone, we recreate this file on the tmpfs.
+This should be all that is required to restore the exact behaviour we would get with a normal clone.
NOTE: If the container is rebooted all changes made to it are lost. This is not easy to prevent since each reboot remounts the rootfs again.
## Configuration changes
-A lot of configuration keys have been renamed to make the experience of configuring a container much more consistent.
+A lot of configuration keys have been renamed to make the experience of configuring a container much more consistent.
LXC 2.1 ensures that all keys that have subkeys are properly namespaces via the "." syntax.
### Network configuration
-The network configuration keys have all been given a new prefix. Some of them have also been renamed.
-From LXC 2.1. onwards network configuration keys using the "lxc.network" prefix are considered deprecated.
-They are replaced by network configuration keys using the new "lxc.net" prefix.
-Furthermore, defining network without indices is marked deprecated.
+The network configuration keys have all been given a new prefix. Some of them have also been renamed.
+From LXC 2.1. onwards network configuration keys using the "lxc.network" prefix are considered deprecated.
+They are replaced by network configuration keys using the new "lxc.net" prefix.
+Furthermore, defining network without indices is marked deprecated.
Consider the following *legacy* network configuration:
lxc.network.type = veth
@@ -584,7 +583,7 @@ Would define two distinct networks. Starting with LXC 2.1 this should be replace
lxc.net.1.link = lxcbr0
lxc.net.1.name = eno1
-Defining networks only in this manner has the advantage of being consistent and order independent.
+Defining networks only in this manner has the advantage of being consistent and order independent.
This means an equivalent configuration for the two networks would be:
lxc.net.1.link = lxcbr0
@@ -598,7 +597,7 @@ This means an equivalent configuration for the two networks would be:
lxc.net.1.name = eno1
-Note that when using multiple definitions of the same key with the same index only the last one
+Note that when using multiple definitions of the same key with the same index only the last one
will be considered by LXC. This is in line with prior LXC version. For example:
lxc.net.2.link = lxcbr0
@@ -656,27 +655,27 @@ The following table lists the legacy configuration keys on the left side and the
lxc.utsname | lxc.uts.name |
### `lxc-update-config` script
-LXC 2.1 comes with a new script `lxc-update-config` which can be used to upgrade existing legacy
+LXC 2.1 comes with a new script `lxc-update-config` which can be used to upgrade existing legacy
LXC configurations to valid LXC 2.1 configurations by simply passing
lxc-update-config -c /path/to/config
-The script will create a backup of the legacy configuration file first.
-The name of the backup config file will by `<original-config-file-name>.backup`.
-The backup is made in case the upgrade does not yield a useable LXC 2.1 config file.
+The script will create a backup of the legacy configuration file first.
+The name of the backup config file will by `<original-config-file-name>.backup`.
+The backup is made in case the upgrade does not yield a useable LXC 2.1 config file.
After creating the backup the script will replace all legacy configuration keys with their new counterparts.
## Deprecation warnings
-LXC 2.1 intends to be fully backward compatible with respect to pre-2.1 configuration files.
-This specifically means that the presence of any deprecated keys should not prevent the container from being useable.
-However, LXC 2.1 will warn about the presence of any deprecated configuration keys.
+LXC 2.1 intends to be fully backward compatible with respect to pre-2.1 configuration files.
+This specifically means that the presence of any deprecated keys should not prevent the container from being useable.
+However, LXC 2.1 will warn about the presence of any deprecated configuration keys.
On container startup LXC 2.1 will warn *once* with the message:
The configuration file contains legacy configuration keys.
Please update your configuration file.
-All users are advised to use the aforementioned `lxc-update-config` script to update their configuration files.
-If the container has logging enabled the log will contain warnings for each detected legacy configuration key.
+All users are advised to use the aforementioned `lxc-update-config` script to update their configuration files.
+If the container has logging enabled the log will contain warnings for each detected legacy configuration key.
This is mostly useful for users who prefer to update their configuration files manually.
# Changelog
@@ -830,10 +829,10 @@ This is mostly useful for users who prefer to update their configuration files m
* tools/lxc-ls: return all containers by default, new filter - list only defined containers.
# Downloads
-The release tarballs may be found on our [download page](https://linuxcontainers.org/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](https://linuxcontainers.org/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.1.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.1).
@@ -843,9 +842,9 @@ This is the eighth bugfix release for LXC 2.0.
Important:
* Security fix for CVE-2017-5985
- * All templates have been updated to not set default passwords anymore,
- instead requiring lxc-attach be used to configure users.
- This may affect some automated environments that were relying on our
+ * All templates have been updated to not set default passwords anymore,
+ instead requiring lxc-attach be used to configure users.
+ This may affect some automated environments that were relying on our
default (very much insecure) users.
Bugfixes:
@@ -950,10 +949,10 @@ Bugfixes:
* start: add crucial details about lxc\_spawn()
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.8.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
@@ -1008,14 +1007,14 @@ Bugfixes:
* lxccontainer: avoid NULL pointer dereference
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.10.
-Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
-The 1.0 branch will keep being supported until June 2019, but at this point,
+Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
+The 1.0 branch will keep being supported until June 2019, but at this point,
only critical bugfixes and security updates will be backported.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -1082,10 +1081,10 @@ The main bugfixes in this release are:
* utils: Add uid, gid, group convenience wrappers
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.7.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
@@ -1206,10 +1205,10 @@ Bugfixes:
* attach: do not send procfd to attached process
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.6.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
@@ -1366,14 +1365,14 @@ Bugfixes:
* attach: do not send procfd to attached process
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.9.
-Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
-The 1.0 branch will keep being supported until June 2019, but at this point,
+Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
+The 1.0 branch will keep being supported until June 2019, but at this point,
only critical bugfixes and security updates will be backported.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -1447,16 +1446,16 @@ The main bugfixes in this release are:
* tools: lxc-checkconfig conditionalize devpts check
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.5.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
## End of life announcement for LXC 1.1 <span class="text-muted">1st of September 2016</span>
LXC 1.1 has now reached its end of life.
-This means that the stable-1.1 branch is now closed and we will not be
+This means that the stable-1.1 branch is now closed and we will not be
doing any more bugfix or security releases for this branch.
Anyone still on LXC 1.1 should upgrade to 2.0 as soon as possible.
@@ -1510,17 +1509,17 @@ The main bugfixes in this release are:
* tests: Add unit tests for lxc\_string\_replace()
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.4.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
## LXC 2.0.3 release announcement <span class="text-muted">28th of June 2016</span>
This is the third bugfix release for LXC 2.0.
-LXC 2.0.3 was released just minutes after LXC 2.0.2 as we spotted an incorrect
+LXC 2.0.3 was released just minutes after LXC 2.0.2 as we spotted an incorrect
AppArmor profile included in the LXC 2.0.2 release tarball.
The main bugfixes in this release are:
@@ -1528,17 +1527,17 @@ The main bugfixes in this release are:
* apparmor: Refresh generated file
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.3.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
## LXC 2.0.2 release announcement <span class="text-muted">28th of June 2016</span>
This is the second bugfix release for LXC 2.0.
-Please do not use LXC 2.0.2, instead use 2.0.3 which fixes
+Please do not use LXC 2.0.2, instead use 2.0.3 which fixes
an accidental regression in AppArmor coverage.
The main bugfixes in this release are:
@@ -1561,10 +1560,10 @@ The main bugfixes in this release are:
* upstart: Force lxc-instance to behave like a good Upstart client
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.2.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
@@ -1610,10 +1609,10 @@ The main bugfixes in this release are:
* templates: tweak to network configuration of the Oracle template
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.1.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
@@ -1704,26 +1703,26 @@ This release was made possible by contributions (720 commits) from a total of 96
* The new cgfsng cgroup backend is now the recommended backend
* lxc.hook.post-stop failures are now fatal to container reboots
-Note that several commands have been significantly reworked in this release.
-We don't consider our command line tools as stable ABI so you may need to test and adapt your scripts,
+Note that several commands have been significantly reworked in this release.
+We don't consider our command line tools as stable ABI so you may need to test and adapt your scripts,
or better, port them to use our stable C API or one of its bindings.
### Deprecation warnings
-The "lxc-clone" and "lxc-start-ephemeral" commands are now considered deprecated and to be replaced by the new lxc-copy.
-Those commands can still be built by using the --enable-legacy flag, however note that they will print a warning when used
+The "lxc-clone" and "lxc-start-ephemeral" commands are now considered deprecated and to be replaced by the new lxc-copy.
+Those commands can still be built by using the --enable-legacy flag, however note that they will print a warning when used
and that they will be removed from upcoming LXC releases.
### Support
-This is the second LXC Long Term Support release which we will be supporting until the 1st of June 2021.
-LXC 1.0, our previous Long Term Support release, is still supported until the 1st of June 2019.
+This is the second LXC Long Term Support release which we will be supporting until the 1st of June 2021.
+LXC 1.0, our previous Long Term Support release, is still supported until the 1st of June 2019.
And lastly, the previous stable release, LXC 1.1 will go end of life on the 1st of September 2016.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.0.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our master branch is on [Github](https://github.com/lxc/lxc/tree/master).
@@ -1927,10 +1926,10 @@ Commands:
Those stable fixes were brought to you by 59 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.8.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -1964,10 +1963,10 @@ Templates:
* ubuntu-cloud: Always exit 1 on error
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.5.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
@@ -2044,10 +2043,10 @@ Templates:
Those stable fixes were brought to you by 14 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.4.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
@@ -2060,9 +2059,9 @@ Important:
* Security fix for CVE-2015-1331
* Security fix for CVE-2015-1334
- * Fix an ABI regression in LXC 1.1 compared to LXC 1.0.
+ * Fix an ABI regression in LXC 1.1 compared to LXC 1.0.
Fixing this unfortunately means that binaries built against LXC
- 1.1.0, 1.1.1 and 1.1.2 will need rebuilding against LXC 1.1.3.
+ 1.1.0, 1.1.1 and 1.1.2 will need rebuilding against LXC 1.1.3.
This is however preferable to not having backward compatibility with
binaries built for LXC 1.0 and its bugfix releases.
@@ -2121,10 +2120,10 @@ Templates:
Those stable fixes were brought to you by 31 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.3.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
@@ -2148,10 +2147,10 @@ This is the second bugfix release for LXC 1.1.
Those stable fixes were brought to you by 9 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.2.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
@@ -2177,37 +2176,37 @@ This is the first bugfix release for LXC 1.1.
Those stable fixes were brought to you by 13 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.1.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
## LXC 1.1.0 release announcement <span class="text-muted">30th of January 2015</span>
The LXC team is pleased to announce the release of LXC 1.1.
-This release will be supported until January 2016 or 2 months after the next release of LXC,
+This release will be supported until January 2016 or 2 months after the next release of LXC,
whichever comes last.
-If you need a long-term supported version of LXC for use in production, we still strongly recommend
+If you need a long-term supported version of LXC for use in production, we still strongly recommend
you stick to LXC 1.0 which is supported with frequent stable releases until April 2019.
-While not strictly required, it is recommended that LXC 1.1 be used with cgmanager 0.35 (or higher)
+While not strictly required, it is recommended that LXC 1.1 be used with cgmanager 0.35 (or higher)
and lxcfs 0.5 (or higher).
### Highlights
-LXC 1.1 introduces checkpoint/restore support for containers through CRIU.
-This allows to serialize the container running state to disk, for live migration or for later local restoration
+LXC 1.1 introduces checkpoint/restore support for containers through CRIU.
+This allows to serialize the container running state to disk, for live migration or for later local restoration
of the container.
-Support for running systemd as the init system inside the container was also greatly improved
-and should now work by default both for privileged and unprivileged containers when combined
+Support for running systemd as the init system inside the container was also greatly improved
+and should now work by default both for privileged and unprivileged containers when combined
with lxcfs and a recent systemd.
-Init scripts have now all been updated to provide the same feature set, which means that a lxcbr0 bridge
-with a DHCP and DNS server (dnsmasq) is now the default for anyone using LXC.
+Init scripts have now all been updated to provide the same feature set, which means that a lxcbr0 bridge
+with a DHCP and DNS server (dnsmasq) is now the default for anyone using LXC.
We currently provide init scripts for systemd, sysvinit and upstart.
This release was made possible by contributions from 84 developers.
@@ -2258,10 +2257,10 @@ This release was made possible by contributions from 84 developers.
* templates: All templates now use lxc.mount.auto = cgroup:mixed proc:mixed sys:mixed (safe default configuration)
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.0, unless they decide to stick to the long term 1.0 release.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our master branch is on [Github](https://github.com/lxc/lxc/tree/master).
@@ -2356,18 +2355,18 @@ Documentation:
Those stable fixes were brought to you by 27 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.7.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
## LXC 1.0.6 release announcement <span class="text-muted">24th of September 2014</span>
This is the sixth bugfix release for the LXC 1.0 series.
-To make supporting both LXC 1.0 and the future LXC 1.1 easier, this version introduces the -F argument to lxc-start.
-This argument is a no-op as lxc-start is already running in the foreground by default, but as that behavior will change in LXC 1.1,
+To make supporting both LXC 1.0 and the future LXC 1.1 easier, this version introduces the -F argument to lxc-start.
+This argument is a no-op as lxc-start is already running in the foreground by default, but as that behavior will change in LXC 1.1,
introducing -F in 1.0 too allows for writing script which will work consistently on upgrades.
### Changes
@@ -2471,10 +2470,10 @@ Documentaiton:
Those stable fixes were brought to you by 24 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.6.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -2482,8 +2481,8 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
This is the fifth bugfix release for the LXC 1.0 series.
### seccomp profile
-Outside of the usual bugfixes, this release also introduces one important change.
-For systems where LXC is built with seccomp support, containers will now have a seccomp profile enabled
+Outside of the usual bugfixes, this release also introduces one important change.
+For systems where LXC is built with seccomp support, containers will now have a seccomp profile enabled
which will prevent calls to the following syscalls:
* kexec\_load
@@ -2494,13 +2493,13 @@ which will prevent calls to the following syscalls:
This will amongst other things prevent exploits like the recently release "shocker" exploit.
-This profile will be applied to any new or existing container that uses the new-style LXC configurations
-(using lxc.include of common configs), so currently the following distributions:
+This profile will be applied to any new or existing container that uses the new-style LXC configurations
+(using lxc.include of common configs), so currently the following distributions:
centos, debian, fedora, gentoo, oracle, plamo and ubuntu.
You can turn this off by adding "lxc.seccomp =" in your container's configuration.
-If you want to manually turn this on for a container which doesn't use the common config mechanism,
+If you want to manually turn this on for a container which doesn't use the common config mechanism,
you can add something like "lxc.seccomp = /usr/share/lxc/config/common.seccomp" to the container configuration.
### Changes
@@ -2554,10 +2553,10 @@ Bindings:
Those stable fixes were brought to you by 11 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.5.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -2589,7 +2588,7 @@ Core:
* core: Fix a null check after dereference (identified by coverity).
* core: Export bdev\_specs so that API users can actually use the functions taking it as an argument.
* core: Don't destroy the container until we've made sure the requested snapshot actually exists.
- * core: Retrieve the container personality over the command interface rather than through /proc.
+ * core: Retrieve the container personality over the command interface rather than through /proc.
This is required for unprivileged containers attach on the 3.15 kernel and higher as access to /proc/$$/personality is now restricted to root.
* core: Fix invalid signal number comparison.
* core: Don't let -lcgmanager end up in LIBS.
@@ -2621,13 +2620,13 @@ Commands:
* lxc-autostart: Backport the autoboot/autostart change.
This is required to resolve problems with autostart on
- systemd systems at least.
+ systemd systems at least.
This change adds support for the NULL group in the -g
option (identified as a comma without any group name).
Add a new special "onboot" group and set the init
scripts (sysvinit, systemd and upstart) to all start
- both the NULL and onboot group.
+ both the NULL and onboot group.
This won't cause any visible change to existing users
unless they were already using an "onboot" group that wasn't
@@ -2666,10 +2665,10 @@ Tests:
Those stable fixes were brought to you by 14 individual contributors.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.4.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -2683,16 +2682,16 @@ Core:
* core: Always initialize netpipe in lxc\_spawn.
* core: Move lxc-monitord.log to LOGPATH instead of LXCPATH.
* core: Make monitord more resilient to unexpected termination.
- * core: Move lxc-init to /sbin/init.lxc instead of the architecture/distro specific multiarch path.
+ * core: Move lxc-init to /sbin/init.lxc instead of the architecture/distro specific multiarch path.
Use path lookup to find it in the container rather than using an hardcoded path.
* core: Set macvlan default mode to private.
* core: Check whether rootfs is shared before running the pre-mount hooks.
- * apparmor: Update the profiles for current upstream apparmor.
- This includes tweak to the pivot\_root targets and the addition of the ptrace and signal stanzas.
- Users of older apparmor versions may want to comment the dbus, ptrace and signal stanzas
+ * apparmor: Update the profiles for current upstream apparmor.
+ This includes tweak to the pivot\_root targets and the addition of the ptrace and signal stanzas.
+ Users of older apparmor versions may want to comment the dbus, ptrace and signal stanzas
if the parser fails to parse the profile.
- * apparmor: Use an intermediary profile which allows for easier generation of complex rules.
- This discovered a few problems with the existing profile which has now been fixed.
+ * apparmor: Use an intermediary profile which allows for easier generation of complex rules.
+ This discovered a few problems with the existing profile which has now been fixed.
Most of /proc/sys is now properly blocked with exceptions for kernel/shm/*, net/*, kernel/domainname and kernel/hostname.
* apparmor: block cgroupfs by default in the with-nesting profile, users should now be using cgmanager which doesn't required this.
* cgmanager: Fix a small cgm\_get bug when len == 0.
@@ -2719,10 +2718,10 @@ Tests:
* tests: Always propagate http\_proxy and https\_proxy.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.3.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -2780,10 +2779,10 @@ Templates:
* opensuse template: Fix syntax error
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.2.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
@@ -2794,7 +2793,7 @@ This is the first bugfix release for the LXC 1.0 series.
Core:
- * core: Detect the use of rshared / and properly work around it.
+ * core: Detect the use of rshared / and properly work around it.
This fixes LXC on systemd systems where the mount table would be duplicated in the container and lxc-attach wouldn't attach to the container's rootfs.
* core: Don't crash on invalid lxc.id\_map
* core: Fix attaching when extra cgroups were setup after the container started
@@ -2827,35 +2826,35 @@ Other:
* upstart: Don't forward requests for LXC\_DOMAIN (dnsmasq)
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.1.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
## LXC 1.0.0 release announcement <span class="text-muted">20th of February 2014</span>
### Introduction
It's with great pleasure that the LXC team is announcing the release of LXC 1.0!
-This release is a significant milestone for us as it marks the first release we consider to be production ready.
-It features a wide variety of improvements to container security, a consistent set of tools,
+This release is a significant milestone for us as it marks the first release we consider to be production ready.
+It features a wide variety of improvements to container security, a consistent set of tools,
updated documentation and an API with multiple bindings.
-Over 60 people contributed their time to this release, making it the best LXC release yet!
-The result of all that work can be seen used in areas as diverse as individual laptops,
-cellphones and cloud instances. And we are confident that with LXC 1.0, we will see LXC's usage expand even more
+Over 60 people contributed their time to this release, making it the best LXC release yet!
+The result of all that work can be seen used in areas as diverse as individual laptops,
+cellphones and cloud instances. And we are confident that with LXC 1.0, we will see LXC's usage expand even more
and be used for a lot of new and exciting projects.
### Downloads
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our main repository is on [Github](https://github.com/lxc/lxc).
### New features
-LXC 1.0 is the result of 10 months of development and over a thousand commits, including a major rework of the way LXC is structured.
-It's therefore near impossible to come up with a comprehensive list of changes in this release,
+LXC 1.0 is the result of 10 months of development and over a thousand commits, including a major rework of the way LXC is structured.
+It's therefore near impossible to come up with a comprehensive list of changes in this release,
however here are some highlights:
* Support for fully unprivileged containers
@@ -2880,20 +2879,20 @@ A series of blog posts introducing you to LXC and highlighting some of LXC 1.0's
### LXC 1.0 moving forward
-LXC 1.0 is the first production ready release of LXC and it comes with a commitment from upstream
-to maintain it until at least Ubuntu 14.04 LTS reaches end of life in April 2019.
+LXC 1.0 is the first production ready release of LXC and it comes with a commitment from upstream
+to maintain it until at least Ubuntu 14.04 LTS reaches end of life in April 2019.
That's slightly over 5 years of support!
-We will be maintaining a separate stable branch and will cherry-pick and backport fixes as appropriate.
-It's expected that we will have frequent bugfix releases of 1.0 so distributions can simply use those
+We will be maintaining a separate stable branch and will cherry-pick and backport fixes as appropriate.
+It's expected that we will have frequent bugfix releases of 1.0 so distributions can simply use those
and save themselves the trouble of having to manually follow our stable branch.
### Bug reports and contact information
-Bug reports should be filed on [Github](https://github.com/lxc/lxc/issues) or if you do not wish to create an account, by e-mail to the appropriate [mailing-list](https://lists.linuxcontainers.org).
+Bug reports should be filed on [Github](https://github.com/lxc/lxc/issues) or if you do not wish to create an account, by e-mail to the appropriate [mailing-list](https://lists.linuxcontainers.org).
The same goes for your patches. We tend to prefer patches sent to lxc-devel but we also accept pull request directly on Github.
-LXC 1.0 is also the first release after the change of project maintainers which occurred in September 2013.
-We'd like to thank Daniel Lezcano for all the great work and efforts he's put in LXC over the years
+LXC 1.0 is also the first release after the change of project maintainers which occurred in September 2013.
+We'd like to thank Daniel Lezcano for all the great work and efforts he's put in LXC over the years
and wish him the best of luck in his new projects!
The current projects maintainers are [Serge Hallyn](https://s3hh.wordpress.com), [Stéphane Graber](https://www.stgraber.org) and [Christian Brauner](https://cbrauner.wordpress.com/)
diff --git a/content/lxcfs/downloads.ja.md b/content/lxcfs/downloads.ja.md
index fdb51f0..07f3e50 100644
--- a/content/lxcfs/downloads.ja.md
+++ b/content/lxcfs/downloads.ja.md
@@ -1,13 +1,13 @@
-
+
# ディストリビューションのパッケージ <!-- Distribution packages -->
<!--
-LXCFS is included in many Linux distributions.
+LXCFS is included in many Linux distributions.
In most cases installing it is as simple as selecting it in your package manager.
-->
LXCFS はたくさんのディストリビューションに含まれています。ほとんどの場合、インストールするには、お使いのパッケージマネージャで LXCFS を選択するだけで簡単です。
<!--
-Distributions also often provide backports of newer versions of LXCFS for their stable releases.
+Distributions also often provide backports of newer versions of LXCFS for their stable releases.
You may want to look for that, especially if your distribution doesn't include LXCFS at all or not the new 2.0 branch.
-->
ディストリビューションでは、stable リリース向けに新しいバージョンの LXCFS のバックポートを提供することがよくあります。特に、お使いのディストリビューションに LXCFS が含まれていない場合や、新しい 2.0 ブランチでない場合には、探してみる必要があるかもしれません。
diff --git a/content/lxcfs/downloads.md b/content/lxcfs/downloads.md
index 224df42..bbb3b84 100644
--- a/content/lxcfs/downloads.md
+++ b/content/lxcfs/downloads.md
@@ -1,9 +1,9 @@
-
+
# Distribution packages
-LXCFS is included in many Linux distributions.
+LXCFS is included in many Linux distributions.
In most cases installing it is as simple as selecting it in your package manager.
-Distributions also often provide backports of newer versions of LXCFS for their stable releases.
+Distributions also often provide backports of newer versions of LXCFS for their stable releases.
You may want to look for that, especially if your distribution doesn't include LXCFS at all or not the new 2.0 branch.
For Ubuntu users, we have an official PPA for LXCFS:
diff --git a/content/lxcfs/downloads.ru.md b/content/lxcfs/downloads.ru.md
index 30299cb..6fdebee 100644
--- a/content/lxcfs/downloads.ru.md
+++ b/content/lxcfs/downloads.ru.md
@@ -1,6 +1,6 @@
-
+
# Пакеты для дистрибутивов
-На данный момент только Ubuntu включает lxcfs и только текущий разрабатываемый релиз.
+На данный момент только Ubuntu включает lxcfs и только текущий разрабатываемый релиз.
Мы ожидаем что скоро другие дистрибутивы, уже предоставляющие cgmanager, включат и ее.
Для пользователей Ubuntu у нас есть официальный PPA для LXCFS:
diff --git a/content/lxcfs/news.md b/content/lxcfs/news.md
index 27c3c5f..bc9708c 100644
--- a/content/lxcfs/news.md
+++ b/content/lxcfs/news.md
@@ -1,4 +1,3 @@
-
# News
## LXCFS 2.0.8 release announcement <span class="text-muted">19th of October 2017</span>
@@ -345,7 +344,7 @@ The release tarballs can be found on our [download page](/lxcfs/downloads/).
## LXCFS 0.4 release announcement <span class="text-muted">23rd of January 2015</span>
Critical bug/security fix update for LXCFS.
-Prior versions of LXCFS would replace the host's /proc with the container's
+Prior versions of LXCFS would replace the host's /proc with the container's
when a read to /proc/uptime was done on a system with / mounted rshared (default on systemd).
This release includes ONLY this bugfix and should be immediately deployed by anyone currently using lxcfs.
@@ -364,7 +363,7 @@ The release tarballs can be found on our [download page](/lxcfs/downloads/).
## LXCFS 0.2 release announcement <span class="text-muted">20th of January 2015</span>
Packager-friendly release of LXCFS 0.2.
-This release now installs /usr/share/lxcfs/lxc.mount.hook and /usr/share/lxc/common.conf.d/00-lxcfs.conf
+This release now installs /usr/share/lxcfs/lxc.mount.hook and /usr/share/lxc/common.conf.d/00-lxcfs.conf
which when combined with LXC 1.1 will automatically enable lxcfs for all containers.
Additionally this release also includes some fixes to the testsuite.
@@ -376,11 +375,11 @@ The release tarballs can be found on our [download page](/lxcfs/downloads/).
## LXCFS 0.1 release announcement <span class="text-muted">9th of January 2015</span>
This is the initial LXCFS release.
-It offers a basic cgroupfs-like interface which writes through CGManager as well as
+It offers a basic cgroupfs-like interface which writes through CGManager as well as
cgroup-ified versions of the cpuinfo, meminfo, stat and uptime proc files.
-Note that as the first release of LXCFS, things can still be very rough and we would advice
+Note that as the first release of LXCFS, things can still be very rough and we would advice
against using this in production.
### Downloads
diff --git a/content/lxd/contribute.ja.md b/content/lxd/contribute.ja.md
index 01c3292..639e0a5 100644
--- a/content/lxd/contribute.ja.md
+++ b/content/lxd/contribute.ja.md
@@ -1,5 +1,3 @@
-
-
# ソースコード <!-- Source code -->
<!--
@@ -10,10 +8,10 @@ LXD の現時点の開発バージョンは Github からクローンできま
git clone git://github.com/lxc/lxd
<!--
-Contributions sent upstream for review must be based on the current git tree
+Contributions sent upstream for review must be based on the current git tree
and not on stable releases, unless the bug only affects a stable release.
-->
-レビューのためにパッチを送る場合は、バグが stable リリースにのみ影響する場合を除いて、stable リリースでなく現時点の開発バージョンのツリーを元にしてください。
+レビューのためにパッチを送る場合は、バグが stable リリースにのみ影響する場合を除いて、stable リリースでなく現時点の開発バージョンのツリーを元にしてください。
# パッチの提案プロセス <!-- Patch submission process -->
<!--
@@ -29,7 +27,7 @@ More details on contribution guidelines may be found [here](https://github.com/l
# 安定版 (stable) リリースへのバックポート <!-- Stable release backports -->
<!--
-In general, all bugfixes will be picked up for the stable release, this however tends to happen in batches
+In general, all bugfixes will be picked up for the stable release, this however tends to happen in batches
every couple of months or so. If we missed a given patch, please file a bug so we can look into it.
-->
一般的には、すべてのバグ修正が安定版リリースに対して適用されます。しかし、この適用は 2〜3 ヶ月程度おきになりがちです。もし、パッチを見逃しているような場合は、調査ができるようにバグ報告をしてください。
diff --git a/content/lxd/contribute.md b/content/lxd/contribute.md
index 0d3ebde..00f6ea0 100644
--- a/content/lxd/contribute.md
+++ b/content/lxd/contribute.md
@@ -1,12 +1,10 @@
-
-
# Source code
The current development version of LXD can be cloned from Github with:
git clone git://github.com/lxc/lxd
-Contributions sent upstream for review must be based on the current git tree
+Contributions sent upstream for review must be based on the current git tree
and not on stable releases, unless the bug only affects a stable release.
# Patch submission process
@@ -17,7 +15,7 @@ More details on contribution guidelines may be found [here](https://github.com/l
# Stable release backports
-In general, all bugfixes will be picked up for the stable release, this however tends to happen in batches
+In general, all bugfixes will be picked up for the stable release, this however tends to happen in batches
every couple of months or so. If we missed a given patch, please file a bug so we can look into it.
Note that only bugfixes are backported to stable releases.
diff --git a/content/lxd/contribute.ru.md b/content/lxd/contribute.ru.md
index 7987182..de8638c 100644
--- a/content/lxd/contribute.ru.md
+++ b/content/lxd/contribute.ru.md
@@ -1,12 +1,10 @@
-
-
# Исходный код
Текущая разрабатываемая версия LXD может быть склонирована с Github:
git clone git://github.com/lxc/lxd
-Патчи, посылаемые в upstream на рассмотрение должны базироваться на текущем дереве git
+Патчи, посылаемые в upstream на рассмотрение должны базироваться на текущем дереве git
а не на стабильных релизах, только если ошибка не затрагивает стабильный релиз.
# Процесс приема патчей
@@ -17,7 +15,7 @@
# Backports в стабильные релизы
-В общем, все исправления ошибок будут добавлены в стабильный релиз, тем не менее, это случается партиями
+В общем, все исправления ошибок будут добавлены в стабильный релиз, тем не менее, это случается партиями
каждые несколько месяцев. Если мы пропустили патч, создайте issue, и мы разберемся.
В стабильные релизы попадут только исправления ошибок.
diff --git a/content/lxd/downloads.ja.md b/content/lxd/downloads.ja.md
index 21a326f..97b0bb8 100644
--- a/content/lxd/downloads.ja.md
+++ b/content/lxd/downloads.ja.md
@@ -1,7 +1,6 @@
-
# ディストリビューションのパッケージ <!-- Distribution packages -->
<!--
-LXD is shipped by a number of Linux distributions.
+LXD is shipped by a number of Linux distributions.
Installation instructions can be found in our [getting started](/lxd/getting-started-cli/) guide.
-->
LXD はたくさんのディストリビューションに含まれています。
diff --git a/content/lxd/downloads.md b/content/lxd/downloads.md
index eefea4a..37cf44d 100644
--- a/content/lxd/downloads.md
+++ b/content/lxd/downloads.md
@@ -1,7 +1,5 @@
-
-
# Distribution packages
-LXD is shipped by a number of Linux distributions.
+LXD is shipped by a number of Linux distributions.
Installation instructions can be found in our [getting started](/lxd/getting-started-cli/) guide.
# Current development version
diff --git a/content/lxd/downloads.ru.md b/content/lxd/downloads.ru.md
index c66c8ff..3a5c077 100644
--- a/content/lxd/downloads.ru.md
+++ b/content/lxd/downloads.ru.md
@@ -1,4 +1,4 @@
-
+
# Пакеты для дистрибутивов
Пользователи Ubuntu 16.04 LTS могут установить LXD с помощью:
diff --git a/content/lxd/getting-started-cli.ja.md b/content/lxd/getting-started-cli.ja.md
index 6a1a46b..4c712f2 100644
--- a/content/lxd/getting-started-cli.ja.md
+++ b/content/lxd/getting-started-cli.ja.md
@@ -1,4 +1,4 @@
-
+
# インストール<!-- Installation -->
## リリースを選択する <!-- Choose your release -->
<!--
@@ -10,7 +10,7 @@ LXD では 2 つのリリースブランチが並行してメンテナンスさ
* フィーチャーリリース <!-- Feature releases -->(LXD 2.x)
<!--
-LTS releases are recommended for production environments as they will benefit from regular bugfix
+LTS releases are recommended for production environments as they will benefit from regular bugfix
and security updates but will not see new features added or any kind of behavioral change.
-->
LTS リリースは本番環境での使用におすすめです。定期的なバグフィックスとセキュリティアップデートが行われますが、新しい機能の追加や動作が変わるような変更は行われないためです。
@@ -150,21 +150,21 @@ This is all done with:
## アクセスコントロール <!-- Access control -->
<!--
-Access control for LXD is based on group membership.
+Access control for LXD is based on group membership.
The root user as well as members of the "lxd" group can interact with the local daemon.
-->
LXD のアクセスコントロールは、グループメンバーシップに基づいて行います。
root ユーザおよび "lxd" グループのメンバーはローカルデーモンと対話できます。
<!--
-If the "lxd" group is missing on your system, create it, then restart the LXD daemon.
+If the "lxd" group is missing on your system, create it, then restart the LXD daemon.
You can then add trusted users to it. Anyone added to this group will have full control over LXD.
-->
"lxd" グループがシステムにない場合は、作成した後、LXD デーモンを再起動します。
そして、信用するユーザを "lxd" グループに追加します。このグループに属するユーザ全員が、LXD を完全に制御できます。
<!--
-Because group membership is normally only applied at login, you may need to either re-open your user session
+Because group membership is normally only applied at login, you may need to either re-open your user session
or use the "newgrp lxd" command in the shell you're going to use to talk to LXD.
-->
グループメンバーシップはログイン時にのみ追加されるので、追加後にあなたのユーザセッションを閉じて再度開くか、LXD と通信したいシェル上で "newgrp lxd" コマンドを実行する必要があります
@@ -185,7 +185,7 @@ That will create and start a new Ubuntu 16.04 container as can be confirmed with
lxc list
<!--
-Your container here is called "first". You also could let LXD give it a random name by
+Your container here is called "first". You also could let LXD give it a random name by
just calling "lxc launch ubuntu:16.04" without a name.
-->
ここで作成し、起動したコンテナは "first" という名前です。"lxc launch ubuntu:16.04" のように名前を指定せずにコマンドを実行し、ランダムな名前になるように LXD を実行することもできます。
@@ -234,7 +234,7 @@ And to remove it entirely:
# コンテナイメージ <!-- Container images -->
<!--
-LXD is image based. Containers must be created from an image and so the image store
+LXD is image based. Containers must be created from an image and so the image store
must get some images before you can do much with LXD.
-->
LXD はイメージベースです。コンテナはイメージから作る必要があります。そして LXD で色々な処理を行う前に、イメージストアにイメージを取得していなければいけません。
@@ -335,7 +335,7 @@ This will prompt you to confirm the remote server fingerprint and then ask you f
このコマンドを実行すると、リモートサーバのフィンガープリントの確認と、パスワードを問い合わせるプロンプトが表示されるはずです。
<!--
-And after that, use all the same command as above but prefixing the container
+And after that, use all the same command as above but prefixing the container
and images name with the remote host like:
-->
そのあとで、コンテナとイメージの前にリモートホスト名をつけて、先のコマンドと同様に使用します:
diff --git a/content/lxd/getting-started-cli.md b/content/lxd/getting-started-cli.md
index f17eaca..3a9b900 100644
--- a/content/lxd/getting-started-cli.md
+++ b/content/lxd/getting-started-cli.md
@@ -1,4 +1,4 @@
-
+
# Installation
## Choose your release
LXD upstream maintains two release branches in parallel:
@@ -6,7 +6,7 @@ LXD upstream maintains two release branches in parallel:
* LTS release (LXD 2.0.x)
* Feature releases (LXD 2.x)
-LTS releases are recommended for production environments as they will benefit from regular bugfix
+LTS releases are recommended for production environments as they will benefit from regular bugfix
and security updates but will not see new features added or any kind of behavioral change.
To get all the latest features and monthly updates to LXD, use the feature release branch instead.
@@ -80,13 +80,13 @@ This is all done with:
sudo lxd init
## Access control
-Access control for LXD is based on group membership.
+Access control for LXD is based on group membership.
The root user as well as members of the "lxd" group can interact with the local daemon.
-If the "lxd" group is missing on your system, create it, then restart the LXD daemon.
+If the "lxd" group is missing on your system, create it, then restart the LXD daemon.
You can then add trusted users to it. Anyone added to this group will have full control over LXD.
-Because group membership is normally only applied at login, you may need to either re-open your user session
+Because group membership is normally only applied at login, you may need to either re-open your user session
or use the "newgrp lxd" command in the shell you're going to use to talk to LXD.
# Creating and using your first container
@@ -98,7 +98,7 @@ That will create and start a new Ubuntu 16.04 container as can be confirmed with
lxc list
-Your container here is called "first". You also could let LXD give it a random name by
+Your container here is called "first". You also could let LXD give it a random name by
just calling "lxc launch ubuntu:16.04" without a name.
Now that your container is running, you can get a shell inside it with:
@@ -126,7 +126,7 @@ And to remove it entirely:
lxc delete first
# Container images
-LXD is image based. Containers must be created from an image and so the image store
+LXD is image based. Containers must be created from an image and so the image store
must get some images before you can do much with LXD.
There are three ways to feed that image store:
@@ -185,7 +185,7 @@ Now to talk to that remote LXD, you can simply add it with:
This will prompt you to confirm the remote server fingerprint and then ask you for the password.
-And after that, use all the same command as above but prefixing the container
+And after that, use all the same command as above but prefixing the container
and images name with the remote host like:
lxc exec host-a:first -- apt-get update
diff --git a/content/lxd/getting-started-cli.ru.md b/content/lxd/getting-started-cli.ru.md
index 8304aa9..97b2225 100644
--- a/content/lxd/getting-started-cli.ru.md
+++ b/content/lxd/getting-started-cli.ru.md
@@ -1,4 +1,4 @@
-
+
# Установка LXD и утилиты командной строки
## Ubuntu desktop and Ubuntu server
@@ -17,33 +17,33 @@
apt-get dist-upgrade
apt-get install lxd
-Пакет создает новую группу "lxd" содержащую всех пользователей, которым разрешено соединятся с
-lxd через локальный unix socket. Все пользователи групп "admin" и "sudoers" добавляются автоматически.
+Пакет создает новую группу "lxd" содержащую всех пользователей, которым разрешено соединятся с
+lxd через локальный unix socket. Все пользователи групп "admin" и "sudoers" добавляются автоматически.
Если ваш пользователь не входит в одну из этих групп, вам необходимо вручную добавить его в группу "lxd".
-Так как членство в группах фиксируется при входе, вам необходимо закрыть
+Так как членство в группах фиксируется при входе, вам необходимо закрыть
и переоткрыть вашу пользовательскую сессию или использовать команду "newgrp lxd" в интерактивной оболочке, в которой вы работаете с lxd.
newgrp lxd
-Затем, для начальной настройки демона LXD, включающей, по вашему пожеланию, настройку оптимизированного хранилища (ZFS),
+Затем, для начальной настройки демона LXD, включающей, по вашему пожеланию, настройку оптимизированного хранилища (ZFS),
а также для обеспечения видимости демона в сети и настройки сети для контейнеров:
sudo lxd init
## Ubuntu Core (snappy)
-LXD доступен для Ubuntu Core как пакет Snap в магазине.
+LXD доступен для Ubuntu Core как пакет Snap в магазине.
Вы можете установить его с помощью:
sudo snappy install lxd.stgraber
После этого, с LXD можно будет взаимодействовать с помощью команды "lxc".
-Следует отметить, что генерация сертификата сервера может занять долгое время, если вы работаете с устройством вроде
+Следует отметить, что генерация сертификата сервера может занять долгое время, если вы работаете с устройством вроде
rpi2, так что может быть, что LXD начнет отвечать на команду lxc только через несколько минут.
## Другие дистрибутивы
-На данный момент существуют пакеты для множества дистрибутивов, включая Gentoo и, конечно, Ubuntu.
+На данный момент существуют пакеты для множества дистрибутивов, включая Gentoo и, конечно, Ubuntu.
Пользователи других дистрибутивов тоже могут найти их в своем менеджере пакетов.
Если их там нет, пожалуйста, загрузите и соберите LXD из git или используя последний релизный tarball.
@@ -51,7 +51,7 @@ rpi2, так что может быть, что LXD начнет отвечат
Инструкции для обоих способов доступны [здесь](/lxd/downloads/).
# Импорт различных образов
-LXD основан на образах. Контейнеры создаются из образа, поэтому хранилище образов
+LXD основан на образах. Контейнеры создаются из образа, поэтому хранилище образов
должно содержать несколько образов перед основной работой с LXD.
Есть несколько путей заполнить хранилище:
@@ -105,7 +105,7 @@ LXD основан на образах. Контейнеры создаются
lxc list
-Ваш контейнер здесь называется "first". Вы можете предоставить LXD выбрать случайное имя
+Ваш контейнер здесь называется "first". Вы можете предоставить LXD выбрать случайное имя
просто вызвав "lxc launch ubuntu" без имени.
Сейчас ваш контейнер запущен, вы можете получить интерактивный доступ внутрь:
@@ -133,7 +133,7 @@ LXD основан на образах. Контейнеры создаются
lxc delete first
# Множество хостов
-Утилита командной строки "lxc" может связываться со множеством серверов LXD.
+Утилита командной строки "lxc" может связываться со множеством серверов LXD.
По умолчанию она связана с локальным по локальному UNIX socket.
Удаленные операции требуют запуска двух команд на удаленном сервере:
@@ -141,7 +141,7 @@ LXD основан на образах. Контейнеры создаются
lxc config set core.https_address "[::]"
lxc config set core.trust_password some-password
-Первая указывает LXD слушать все адреса на порту 8443.
+Первая указывает LXD слушать все адреса на порту 8443.
Вторая устанавливает надежный пароль для связи с сервером.
Теперь для связи с удаленным LXD, вы можете просто добавить его:
@@ -150,7 +150,7 @@ LXD основан на образах. Контейнеры создаются
Это попросит вас подтвердить отпечаток удаленного сервера а затем спросит пароль.
-И после этого, используйте те же команды, что и раньше, но предваряя из именами контейнера
+И после этого, используйте те же команды, что и раньше, но предваряя из именами контейнера
и образа:
lxc exec host-a:first -- apt-get update
diff --git a/content/lxd/getting-started-openstack.ja.md b/content/lxd/getting-started-openstack.ja.md
index eb4d0a1..8e94975 100644
--- a/content/lxd/getting-started-openstack.ja.md
+++ b/content/lxd/getting-started-openstack.ja.md
@@ -1,4 +1,4 @@
-
+
# Nova LXD のインストールと設定 <!-- Installing and configuring Nova LXD -->
@@ -29,7 +29,7 @@ containers:
sudo service nova-compute restart
<!--
-In order to support migration of containers between Compute hosts, LXD must be configured to listen for network
+In order to support migration of containers between Compute hosts, LXD must be configured to listen for network
connections and a trust password must be set:
-->
Compute ホスト間のコンテナのマイグレーションをサポートするために、LXD はネットワーク接続を listen するように設定され、パスワードが設定されている必要があります。
@@ -47,13 +47,13 @@ Each Nova LXD instance within your deployment must then be configured with remot
## Juju を使った自動デプロイ <!-- Automated deployment using Juju -->
<!--
-Deploying OpenStack is a complex process, for which a number of deployment tools exist; Juju provides a nice way
+Deploying OpenStack is a complex process, for which a number of deployment tools exist; Juju provides a nice way
to deploy OpenStack on Ubuntu, and a specific [bundle of charms](https://jujucharms.com/u/openstack-charmers-next/openstack-lxd) can be used to deploy OpenStack cloud using LXD.
-->
OpenStack のデプロイは複雑なプロセスが必要で、それを行うためのツールが多数存在しています。Juju は Ubuntu 上で OpenStack をデプロイするのに良い手段を提供しています。LXD を使った OpenStack クラウドのデプロイに、専用の [Charm の Bundle](https://jujucharms.com/u/openstack-charmers-next/openstack-lxd) が使えます。
<!--
-The bundle automatically configures storage for containers root filesystems using LVM and sets up appropriate network configuration,
+The bundle automatically configures storage for containers root filesystems using LVM and sets up appropriate network configuration,
trust passwords and remotes to support migration of containers between LXD hypervisors.
-->
Bundle が LVM を使ってコンテナルートファイルシステム用のストレージを設定します。そして、適切なネットワークの設定、パスワード、LXD ハイパーバイザ間のコンテナのマイグレーションをサポートするためのリモートホストを設定します。
@@ -79,7 +79,7 @@ LXD コンテナは KVM コンテナと同じ方法で管理します。Horizon
nova boot --image=trusty --flavor=m1.tiny my-first-openstack-lxd-container
<!--
-You may need to associate a floating ip address and configure appropriate security rules, depending on the network and
+You may need to associate a floating ip address and configure appropriate security rules, depending on the network and
security configuration of the OpenStack cloud you are using.
-->
Floating IP アドレスを追加したり、お使いのネットワークと OpenStack クラウドのセキュリティ設定から決まる適切なセキュリティルールを設定する必要があるかもしれません。
diff --git a/content/lxd/getting-started-openstack.md b/content/lxd/getting-started-openstack.md
index 07cb2c3..df4d6d7 100644
--- a/content/lxd/getting-started-openstack.md
+++ b/content/lxd/getting-started-openstack.md
@@ -1,4 +1,4 @@
-
+
# Installing and configuring Nova LXD
@@ -18,7 +18,7 @@ containers:
sudo usermod -G lxd -a nova
sudo service nova-compute restart
-In order to support migration of containers between Compute hosts, LXD must be configured to listen for network
+In order to support migration of containers between Compute hosts, LXD must be configured to listen for network
connections and a trust password must be set:
sudo lxc config set core.https_address [::]
@@ -30,10 +30,10 @@ Each Nova LXD instance within your deployment must then be configured with remot
## Automated deployment using Juju
-Deploying OpenStack is a complex process, for which a number of deployment tools exist; Juju provides a nice way
+Deploying OpenStack is a complex process, for which a number of deployment tools exist; Juju provides a nice way
to deploy OpenStack on Ubuntu, and a specific [bundle of charms](https://jujucharms.com/u/openstack-charmers-next/openstack-lxd) can be used to deploy OpenStack cloud using LXD.
-The bundle automatically configures storage for containers root filesystems using LVM and sets up appropriate network configuration,
+The bundle automatically configures storage for containers root filesystems using LVM and sets up appropriate network configuration,
trust passwords and remotes to support migration of containers between LXD hypervisors.
## LXD images for OpenStack
@@ -50,5 +50,5 @@ LXD containers are managed in the same manner as KVM containers - either via Hor
nova boot --image=trusty --flavor=m1.tiny my-first-openstack-lxd-container
-You may need to associate a floating ip address and configure appropriate security rules, depending on the network and
+You may need to associate a floating ip address and configure appropriate security rules, depending on the network and
security configuration of the OpenStack cloud you are using.
diff --git a/content/lxd/getting-started-openstack.ru.md b/content/lxd/getting-started-openstack.ru.md
index 0678d4d..fd2b84a 100644
--- a/content/lxd/getting-started-openstack.ru.md
+++ b/content/lxd/getting-started-openstack.ru.md
@@ -1,4 +1,4 @@
-
+
# Установка и настройка Nova LXD
@@ -18,7 +18,7 @@ LXD:
sudo usermod -G lxd -a nova
sudo service nova-compute restart
-Для поддержки миграции контейнеров между хостами Compute, LXD должен быть настроен на прием соединений
+Для поддержки миграции контейнеров между хостами Compute, LXD должен быть настроен на прием соединений
из сети, и установлен надежный пароль:
sudo lxc config set core.https_address [::]
@@ -30,15 +30,15 @@ LXD:
## Автоматическое развертывание с Juju
-Развертывание OpenStack это сложный процесс, для его осуществления существует несколько утилит развертывания; Juju предлагает удобный вариант
+Развертывание OpenStack это сложный процесс, для его осуществления существует несколько утилит развертывания; Juju предлагает удобный вариант
развертывания OpenStack на Ubuntu, а специальный [волшебный пакет](https://jujucharms.com/u/openstack-charmers-next/openstack-lxd) может быть использован для развертывания OpenStack cloud с LXD.
-Пакет автоматически настраивает хранилище для корневых систем контейнеров с использованием LVM и устанавливает подходящие настройки сети,
+Пакет автоматически настраивает хранилище для корневых систем контейнеров с использованием LVM и устанавливает подходящие настройки сети,
надежные пароли и удаленные подключения для поддержки миграции контейнеров между гипервизорами LXD.
## Образы LXD для OpenStack
-LXD не поддерживает использование формата образов qcow2 KVM; LXD требуются образы на основе файловой системы "raw".
+LXD не поддерживает использование формата образов qcow2 KVM; LXD требуются образы на основе файловой системы "raw".
Canonical публикует образы Ubuntu images в требуемом формате:
glance image-create --name="trusty" --public --progress \
@@ -51,5 +51,5 @@ Canonical публикует образы Ubuntu images в требуемом ф
nova boot --image=trusty --flavor=m1.tiny my-first-openstack-lxd-container
-Вам может понадобится присвоить временный IP адрес и настроить необходимые политики безопасности в зависимости от сети и
+Вам может понадобится присвоить временный IP адрес и настроить необходимые политики безопасности в зависимости от сети и
настроек безопасности используемого вами OpenStack cloud.
diff --git a/content/lxd/introduction.ja.md b/content/lxd/introduction.ja.md
index 43cbc5f..c3a7dfe 100644
--- a/content/lxd/introduction.ja.md
+++ b/content/lxd/introduction.ja.md
@@ -1,41 +1,41 @@
-
+
# LXD とは? <!-- What's LXD? -->
<!--
-LXD is a next generation system container manager.
+LXD is a next generation system container manager.
It offers a user experience similar to virtual machines but using Linux containers instead.
-->
LXD は次世代のシステムコンテナマネージャです。
仮想マシンと同じようなユーザ体験を提供しますが、仮想マシンではなく Linux コンテナを使います。
<!--
-It's image based with pre-made images available for a [wide number of Linux distributions](https://images.linuxcontainers.org)
+It's image based with pre-made images available for a [wide number of Linux distributions](https://images.linuxcontainers.org)
and is built around a very powerful, yet pretty simple, REST API.
-->
LXD は、[多数の Linux ディストリビューション](https://images.linuxcontainers.org)が利用できる、あらかじめビルドされたイメージをベースとしています。そして、とてもパワフルでありながら、とてもシンプルな REST API を中心に構成されています。
<!--
-To get a better idea of what LXD is and what it does, you can [try it online](/lxd/try-it/)!
+To get a better idea of what LXD is and what it does, you can [try it online](/lxd/try-it/)!
Then if you want to run it locally, take a look at our [getting started guide](/lxd/getting-started-cli/).
-->
LXD がどのようなもので、何ができるのかをよく理解するために、[オンラインで使ってみる](/ja/lxd/try-it/)ことができます!
さらに、LXD をローカルで実行したい場合は、[「はじめに」](/ja/lxd/getting-started-cli/) のページをご覧ください。
<!--
-The LXD project was founded and is currently led by [Canonical Ltd](https://www.canonical.com)
+The LXD project was founded and is currently led by [Canonical Ltd](https://www.canonical.com)
with contributions from a range of other companies and individual contributors.
-->
LXD プロジェクトは [Canonical Ltd](http://www.canonical.com) によって設立され、現在は様々な企業や個人のコントリビュータの貢献のもとで [Canonical Ltd](http://www.canonical.com) が主導しています。
# デザイン <!-- Design -->
<!--
-The core of LXD is a privileged daemon which exposes a REST API over a local unix socket
+The core of LXD is a privileged daemon which exposes a REST API over a local unix socket
as well as over the network (if enabled).
-->
LXD のコアは、ローカルの UNIX ソケットとネットワーク経由 (有効になっている場合) で REST API を提供する特権デーモンです。
<!--
-Clients, such as the command line tool provided with LXD itself then do everything through that REST API.
+Clients, such as the command line tool provided with LXD itself then do everything through that REST API.
It means that whether you're talking to your local host or a remote server, everything works the same way.
-->
LXD に付属するコマンドラインツールのようなクライアントは、この REST API を通してすべての操作を行います。
@@ -59,13 +59,13 @@ LXDの主要な特長には以下のようなものがあります:
# OpenStack との統合 <!-- Integration with OpenStack -->
<!--
-The "nova-lxd" project provides an OpenStack Nova plugin that seemlessly integrates
+The "nova-lxd" project provides an OpenStack Nova plugin that seemlessly integrates
system containers into a regular OpenStack deployment.
-->
"nova-lxd" プロジェクトが提供する OpenStack Nova プラグインは、システムコンテナを通常の OpenStack のデプロイメントにシームレスに統合します。
<!--
-With this, users will either get a virtual machine or a container, simply depending on what image or
+With this, users will either get a virtual machine or a container, simply depending on what image or
instance type they select. It's completely transparent and works with the regular OpenStack APIs.
-->
これにより、ユーザは選択したイメージまたはインスタンスタイプに応じて、仮想マシンまたはコンテナが得られます。完全に透過的で、通常の OpenStack API で動作します。
@@ -77,7 +77,7 @@ LXD と OpenStack について更に知りたい場合は、[「はじめに - O
# 可用性 <!-- Availability -->
<!--
-LXD works on any recent Linux distribution. LXD upstream directly maintains the Ubuntu packages
+LXD works on any recent Linux distribution. LXD upstream directly maintains the Ubuntu packages
and also publishes a snap package which can be used with most of the popular Linux distributions.
-->
LXD は最近の Linux ディストリビューションで動作します。LXD 開発元は、直接 Ubuntu のパッケージのメンテナンスを行っています。そして、主要な Linux ディストリビューションのほとんどで使える snap パッケージのリリースも行っています。
@@ -89,15 +89,15 @@ More details can be found on our [getting started](/lxd/getting-started-cli/) pa
# LXC との関係 <!-- Relationship with LXC -->
<!--
-LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new,
-better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding
+LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new,
+better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding
to create and manage the containers.
-->
LXD は LXC の書き直しではありません。実際 LXD は新しい、より良いユーザ体験を提供するために LXC 上で構築されています。
LXD はコンテナを作成したり管理したりするために liblxc とその Go バインディングを通して LXC を利用しています。
<!--
-It's basically an alternative to LXC's tools and distribution template system
+It's basically an alternative to LXC's tools and distribution template system
with the added features that come from being controllable over the network.
-->
LXD は基本的には LXC ツールとディストリビューションテンプレートの仕組みの代わりとなる新しいもので、ネットワーク経由でコントロールできる特長を追加したものです。
@@ -109,7 +109,7 @@ LXD is written in Go, it's free software and is developed under the Apache 2 lic
LXD は Go で書かれています。フリーソフトウェアであり、Apache 2 ライセンスのもとで開発されています。
<!--
-There are no CLA or similar legal agreements required to contribute to LXD,
+There are no CLA or similar legal agreements required to contribute to LXD,
however we do require commits be signed-off (following the DCO - Developer Certificate of Ownership).
-->
LXD に貢献するのに必要な CLA や同様の法的合意はありません。しかし、コミットを signed-off する必要があります (DCO - Developer Certificate of Ownership に従います)。
@@ -124,14 +124,14 @@ LXD には二種類のリリースがあります:
* Feature (新機能) リリース <!-- Feature releases -->
<!--
-The current LTS is LXD 2.0 which is supported until June 2021 and gets frequent bugfix and security updates
+The current LTS is LXD 2.0 which is supported until June 2021 and gets frequent bugfix and security updates
but does not receive any feature addition.
-->
現在の LTS は LXD 2.0 で、2021 年 6 月までサポートされます。LTS ではバグフィックスとセキュリティアップデートを受けられますが、機能の追加は行われません。
<!--
-Feature releases are pushed out every month or so and contain new features as well as bugfixes.
-The normal support length for those releases is of about a month, or until the next one comes out.
+Feature releases are pushed out every month or so and contain new features as well as bugfixes.
+The normal support length for those releases is of about a month, or until the next one comes out.
Some Linux distributions may offer longer support for particular feature releases that they decided to ship.
-->
Feature リリースは毎月リリースされ、バグフィックスと新機能が含まれています。通常のサポート期間は約一ヶ月か、次のリリースが行われるまでです。
diff --git a/content/lxd/introduction.md b/content/lxd/introduction.md
index a76b512..9dd8b43 100644
--- a/content/lxd/introduction.md
+++ b/content/lxd/introduction.md
@@ -1,23 +1,23 @@
-
+
# What's LXD?
-LXD is a next generation system container manager.
+LXD is a next generation system container manager.
It offers a user experience similar to virtual machines but using Linux containers instead.
-It's image based with pre-made images available for a [wide number of Linux distributions](https://images.linuxcontainers.org)
+It's image based with pre-made images available for a [wide number of Linux distributions](https://images.linuxcontainers.org)
and is built around a very powerful, yet pretty simple, REST API.
-To get a better idea of what LXD is and what it does, you can [try it online](/lxd/try-it/)!
+To get a better idea of what LXD is and what it does, you can [try it online](/lxd/try-it/)!
Then if you want to run it locally, take a look at our [getting started guide](/lxd/getting-started-cli/).
-The LXD project was founded and is currently led by [Canonical Ltd](https://www.canonical.com)
+The LXD project was founded and is currently led by [Canonical Ltd](https://www.canonical.com)
with contributions from a range of other companies and individual contributors.
# Design
-The core of LXD is a privileged daemon which exposes a REST API over a local unix socket
+The core of LXD is a privileged daemon which exposes a REST API over a local unix socket
as well as over the network (if enabled).
-Clients, such as the command line tool provided with LXD itself then do everything through that REST API.
+Clients, such as the command line tool provided with LXD itself then do everything through that REST API.
It means that whether you're talking to your local host or a remote server, everything works the same way.
# Features
@@ -34,32 +34,32 @@ Some of the biggest features of LXD are:
* Storage management (support for multiple storage backends, storage pools and storage volumes)
# Integration with OpenStack
-The "nova-lxd" project provides an OpenStack Nova plugin that seemlessly integrates
+The "nova-lxd" project provides an OpenStack Nova plugin that seemlessly integrates
system containers into a regular OpenStack deployment.
-With this, users will either get a virtual machine or a container, simply depending on what image or
+With this, users will either get a virtual machine or a container, simply depending on what image or
instance type they select. It's completely transparent and works with the regular OpenStack APIs.
To learn more about LXD and OpenStack, take a look at our [getting started with OpenStack](/lxd/getting-started-openstack/) page.
# Availability
-LXD works on any recent Linux distribution. LXD upstream directly maintains the Ubuntu packages
+LXD works on any recent Linux distribution. LXD upstream directly maintains the Ubuntu packages
and also publishes a snap package which can be used with most of the popular Linux distributions.
More details can be found on our [getting started](/lxd/getting-started-cli/) page.
# Relationship with LXC
-LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new,
-better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding
+LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new,
+better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding
to create and manage the containers.
-It's basically an alternative to LXC's tools and distribution template system
+It's basically an alternative to LXC's tools and distribution template system
with the added features that come from being controllable over the network.
# Language, licensing and contributions
LXD is written in Go, it's free software and is developed under the Apache 2 license.
-There are no CLA or similar legal agreements required to contribute to LXD,
+There are no CLA or similar legal agreements required to contribute to LXD,
however we do require commits be signed-off (following the DCO - Developer Certificate of Ownership).
# Support
@@ -68,11 +68,11 @@ LXD has two kind of releases:
* LTS releases
* Feature releases
-The current LTS is LXD 2.0 which is supported until June 2021 and gets frequent bugfix and security updates
+The current LTS is LXD 2.0 which is supported until June 2021 and gets frequent bugfix and security updates
but does not receive any feature addition.
-Feature releases are pushed out every month or so and contain new features as well as bugfixes.
-The normal support length for those releases is of about a month, or until the next one comes out.
+Feature releases are pushed out every month or so and contain new features as well as bugfixes.
+The normal support length for those releases is of about a month, or until the next one comes out.
Some Linux distributions may offer longer support for particular feature releases that they decided to ship.
Commercial support for LXD on Ubuntu LTS releases can be obtained from [Canonical Ltd](http://www.canonical.com).
diff --git a/content/lxd/introduction.ru.md b/content/lxd/introduction.ru.md
index 4174c70..42455c3 100644
--- a/content/lxd/introduction.ru.md
+++ b/content/lxd/introduction.ru.md
@@ -1,4 +1,4 @@
-
+
# Что такое LXD?
LXD - это гипервизор контейнеров, который базируется на LXC.
diff --git a/content/lxd/news.md b/content/lxd/news.md
index 8252e57..616d694 100644
--- a/content/lxd/news.md
+++ b/content/lxd/news.md
@@ -1,3 +1,3 @@
-
+
# News
diff --git a/content/lxd/rest-api.ja.md b/content/lxd/rest-api.ja.md
index 20cf24f..edc9b10 100644
--- a/content/lxd/rest-api.ja.md
+++ b/content/lxd/rest-api.ja.md
@@ -1,4 +1,4 @@
-
+
# LXD の API <!-- The LXD API -->
@@ -8,7 +8,7 @@ LXD currently only implements a single version of the API, called "1.0".
LXD では、現時点で "1.0" と呼ばれる単一のバージョンの API のみが実装されています。
<!--
-Details on that API can be found at:
+Details on that API can be found at:
[https://github.com/lxc/lxd/blob/master/doc/rest-api.md](https://github.com/lxc/lxd/blob/master/doc/rest-api.md)
-->
API の詳細は以下でご覧いただけます:
@@ -17,7 +17,7 @@ API の詳細は以下でご覧いただけます:
## API の後方互換性 <!-- API backward compatibility -->
<!--
-Once an API is marked as "stable", as is the case with the 1.0 API. We commit not to do any backward incompatible changes to it.
+Once an API is marked as "stable", as is the case with the 1.0 API. We commit not to do any backward incompatible changes to it.
We will however make API additions which will be accompanied by an identifier which newer clients can look for.
-->
1.0 API のように、一度 API が "stable" とマークされた時点で、それに対する後方互換性を壊す変更をしないことを約束します。
diff --git a/content/lxd/rest-api.md b/content/lxd/rest-api.md
index 64c5544..5a38ffa 100644
--- a/content/lxd/rest-api.md
+++ b/content/lxd/rest-api.md
@@ -1,15 +1,15 @@
-
+
# The LXD API
LXD currently only implements a single version of the API, called "1.0".
-Details on that API can be found at:
+Details on that API can be found at:
[https://github.com/lxc/lxd/blob/master/doc/rest-api.md](https://github.com/lxc/lxd/blob/master/doc/rest-api.md)
## API backward compatibility
-Once an API is marked as "stable", as is the case with the 1.0 API. We commit not to do any backward incompatible changes to it.
+Once an API is marked as "stable", as is the case with the 1.0 API. We commit not to do any backward incompatible changes to it.
We will however make API additions which will be accompanied by an identifier which newer clients can look for.
This means that newer clients can detect whether a given target server supports the new feature and only use it if it does.
diff --git a/content/lxd/rest-api.ru.md b/content/lxd/rest-api.ru.md
index f8f3832..5022813 100644
--- a/content/lxd/rest-api.ru.md
+++ b/content/lxd/rest-api.ru.md
@@ -1,15 +1,15 @@
-
+
# API LXD
На данный момент LXD реализует только одну версию API, обозначаемую как "1.0".
-Информация по API может быть найдена на:
+Информация по API может быть найдена на:
[https://github.com/lxc/lxd/blob/master/doc/rest-api.md](https://github.com/lxc/lxd/blob/master/doc/rest-api.md)
## Обратная совместимость
-Как только API отмечено как "стабильное", как в случае с версией API 1.0, мы соглашаемся не вносить в него никаких обратно несовместимых изменений.
+Как только API отмечено как "стабильное", как в случае с версией API 1.0, мы соглашаемся не вносить в него никаких обратно несовместимых изменений.
Тем не менее, мы будем дополнять API, отмечая версии идентификатором для удобства новых пользователей.
Это значит, что новые пользователи смогут отследить, поддерживает ли выбранный сервер нужную возможность, и решить вопрос с ее использованием.
diff --git a/content/lxd/try-it.html b/content/lxd/try-it.html
index 7eec9e4..b0985b3 100644
--- a/content/lxd/try-it.html
+++ b/content/lxd/try-it.html
@@ -7,94 +7,104 @@
<div class="row">
<div class="col-12">
<noscript>
- <div class="panel panel-danger">
- <div class="panel-heading">JavaScript required</div>
-
- <div class="panel-body">
- <p>The LXD demo service client is entirely JavaScript based.</p>
-
- <p>It appears the your web browser doesn't support JavaScript or
- that you or an extension you installed is disabling
- JavaScript for this site.</p>
-
- <p>To use this service, you will need to enable JavaScript support
- and refresh the page.</p>
+ <div class="p-notification--negative">
+ <div class="p-notification__response">
+ <span class="p-notification__status">JavaScript required</span>
+
+ <div class="p-notification__body">
+ <p>The LXD demo service client is entirely JavaScript based.</p>
+ <p>It appears the your web browser doesn't support JavaScript or
+ that you or an extension you installed is disabling
+ JavaScript for this site.</p>
+ <p>To use this service, you will need to enable JavaScript support
+ and refresh the page.</p>
+ </div>
</div>
</div>
</noscript>
- <div class="panel panel-success" id="tryit_status_panel" style="display:none">
- <div class="panel-heading">Server status</div>
- <div class="panel-body" id="tryit_online_message" style="display:none">
- You are connected over: <span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
- The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span>
- </div>
-
- <div class="panel-body" id="tryit_maintenance_message" style="display:none">
- The demo service is currently down for maintenance and should be
- back online in a few minutes.
- </div>
-
- <div class="panel-body" id="tryit_unreachable_message" style="display:none">
- Your browser couldn't reach the demo server.<br />
- This is either (most likely) because of a firewall or proxy
- issue on your side or because of a network, power or other catastrophic
- server side failure.
- </div>
+ <div class="p-notification--negative" id="tryit_status_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">Server status</span>
+ <span class="p-notification__body" id="tryit_online_message" style="display:none">
+ You are connected over: <span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
+ The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span>
+ </span>
+
+ <span class="p-notification__body" id="tryit_maintenance_message" style="display:none">
+ The demo service is currently down for maintenance and should be
+ back online in a few minutes.
+ </span>
+
+ <span class="p-notification__body" id="tryit_unreachable_message" style="display:none">
+ Your browser couldn't reach the demo server.<br />
+ This is either (most likely) because of a firewall or proxy
+ issue on your side or because of a network, power or other catastrophic
+ server side failure.
+ </span>
+ </p>
</div>
- <div class="panel panel-primary" id="tryit_terms_panel" style="display:none">
- <div class="panel-heading">Terms of service</div>
- <div class="panel-body" id="tryit_terms"></div>
+ <div class="p-notification--information" id="tryit_terms_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">Terms of service</span>
+ <div class="p-notification__body" id="tryit_terms"></div>
+ </p>
</div>
- <div class="panel panel-warning" id="tryit_start_panel" style="display:none">
- <div class="panel-heading">Start</div>
- <div class="panel-body">
- <button class="btn btn-default btn-lg" id="tryit_accept" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-ok"></span>
- I have read and accept the terms of service above
- </button>
+ <div class="p-notification--caution" id="tryit_start_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">Start</span>
+ <div class="p-notification__body">
+ <button class="p-button" id="tryit_accept" type="button">
+ <i aria-hidden="true" class="p-icon--success"></i>
+ I have read and accept the terms of service above
+ </button>
- <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
- <p>
- <big>Starting the container...</big>
- </p>
- <p>
- <div class="large spinner"></div>
- </p>
+ <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
+ <p class="p-heading--four">Starting the container...</p>
+ <p>
+ <i class="p-icon--spinner u-animation--spin"></i>
+ </p>
+ </div>
</div>
- </div>
+ </p>
</div>
- <div class="panel panel-success" id="tryit_info_panel" style="display:none">
- <div class="panel-heading">Container information</div>
- <table class="table" style="padding-left: 15px;">
- <tr id="tryit_lxd_row">
- <th>Remote LXD</th>
- <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
- </tr>
-
- <tr id="tryit_clock">
- <th>Remaining time</th>
- <td><span class="minutes"></span> minutes, <span class="seconds"></span> seconds</td>
- </tr>
- </table>
+ <div class="p-notification--positive" id="tryit_info_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status">Container information</span>
+ <div class="p-notification__body">
+ <table class="table">
+ <tr id="tryit_lxd_row">
+ <th>Remote LXD</th>
+ <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
+ </tr>
+
+ <tr id="tryit_clock">
+ <th>Remaining time</th>
+ <td><span class="minutes"></span> minutes, <span class="seconds"></span> seconds</td>
+ </tr>
+ </table>
+ </div>
+ </div>
</div>
- <div class="panel panel-primary" id="tryit_console_panel" style="display:none">
- <div class="panel-heading">Terminal</div>
- <div id="tryit_console" style="background-color:black;"></div>
+ <div class="p-notification" id="tryit_console_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status">Terminal</span>
+ <div id="tryit_console" style="background-color:black;"></div>
- <button class="btn btn-default btn-lg" id="tryit_console_reconnect" type="button" style="display:none">
- <span aria-hidden="true" class="glyphicon glyphicon-repeat"></span>
- Reconnect
- </button>
+ <button class="p-button" id="tryit_console_reconnect" type="button" style="display:none">
+ Reconnect
+ </button>
+ </div>
</div>
- <div class="panel panel-warning" id="tryit_examples_panel" style="display:none">
- <div class="panel-heading"><a data-toggle="collapse" class="text" href="#tryit_examples_collapse">Step by step instructions</a></div>
- <div class="panel-body collapse in" id="tryit_examples_collapse">
+ <div class="p-notification--caution" id="tryit_examples_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status"><a href="#introduction">Step by step instructions</a></span>
+
<ul class="nav nav-tabs" style="display:none">
<li class="active"><a href="#introduction" data-toggle="tab">Introduction</a></li>
<li><a href="#first-container" data-toggle="tab">Your first container</a></li>
@@ -106,349 +116,382 @@
<li><a href="#remote-lxd" data-toggle="tab">Interact with remote LXD servers</a></li>
<li><a href="#conclusion" data-toggle="tab">Conclusion</a></li>
</ul>
+ <div class="tab-content" id="introduction">
+ <h3>Introduction</h3>
+ <p>You are now root inside a LXD container with a
+ nested LXD installed inside it.
+ </p>
- <div class="tab-content">
- <div class="tab-pane fade in active" id="introduction">
- <h3>Introduction</h3>
- <p>You are now root inside a LXD container with a
- nested LXD installed inside it.
- </p>
-
- <p>Initial startup can take a few seconds due to
- having to generate SSL keys on a rather busy system.
- <br />
- Further commands should then be near instantaneous.
- </p>
+ <p>Initial startup can take a few seconds due to
+ having to generate SSL keys on a rather busy system.
+ <br />
+ Further commands should then be near instantaneous.
+ </p>
- <p>You're welcome to just poke around and
- discover LXD through its manpage and --help
- option.
- <br />
- Or you can follow this step by step tutorial
- instead which will get you through LXD's
- main features.
- </p>
+ <p>You're welcome to just poke around and
+ discover LXD through its manpage and --help
+ option.
+ <br />
+ Or you can follow this step by step tutorial
+ instead which will get you through LXD's
+ main features.
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="disabled"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#" class="p-button is--disabled" aria-disabled="true">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#first-container" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="first-container">
- <h3>Your first container</h3>
+ <div class="tab-content" id="first-container">
+ <h3>Your first container</h3>
- <p>LXD is image based, however by default no
- images are loaded into the image store as can
- be seen with: <pre>lxc image list</pre>
- </p>
+ <p>LXD is image based, however by default no
+ images are loaded into the image store as can
+ be seen with: <pre>lxc image list</pre>
+ </p>
- <p>LXD knows about 3 default image servers:
- <ul>
- <li>ubuntu: (for Ubuntu stable images)</li>
- <li>ubuntu-daily: (for Ubuntu daily images)</li>
- <li>images: (for a bunch of other distributions)</li>
- </ul>
- </p>
+ <p>LXD knows about 3 default image servers:
+ <ul>
+ <li>ubuntu: (for Ubuntu stable images)</li>
+ <li>ubuntu-daily: (for Ubuntu daily images)</li>
+ <li>images: (for a bunch of other distributions)</li>
+ </ul>
+ </p>
- <p>The stable Ubuntu images can be listed with:
- <pre>lxc image list ubuntu: | less</pre>
- </p>
+ <p>The stable Ubuntu images can be listed with:
+ <pre>lxc image list ubuntu: | less</pre>
+ </p>
- <p>To launch a first container called "first"
- using the Ubuntu 16.04 image, use:
- <pre>lxc launch ubuntu:16.04 first</pre>
- </p>
+ <p>To launch a first container called "first"
+ using the Ubuntu 16.04 image, use:
+ <pre>lxc launch ubuntu:16.04 first</pre>
+ </p>
- <p>Your new container will now be visible in:
- <pre>lxc list</pre>
- </p>
+ <p>Your new container will now be visible in:
+ <pre>lxc list</pre>
+ </p>
- <p>Running state details and configuration can
- be queried with:
- <pre>lxc info first
- lxc config show first</pre>
- </p>
+ <p>Running state details and configuration can
+ be queried with:
+ <pre>lxc info first
+ lxc config show first</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#introduction" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#limiting-resources" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="limiting-resources">
- <h3>Limiting resources</h3>
+ <div class="tab-content" id="limiting-resources">
+ <h3>Limiting resources</h3>
- <p>By default your container comes with no
- resource limitation and inherits from its
- parent environment. You can confirm it with:
- <pre>free -m
- lxc exec first -- free -m</pre>
- </p>
+ <p>By default your container comes with no
+ resource limitation and inherits from its
+ parent environment. You can confirm it with:
+ <pre>free -m
+ lxc exec first -- free -m</pre>
+ </p>
- <p>To apply a memory limit to your container, do:
- <pre>lxc config set first limits.memory 128MB</pre>
- </p>
+ <p>To apply a memory limit to your container, do:
+ <pre>lxc config set first limits.memory 128MB</pre>
+ </p>
- <p>And confirm that it's been applied with:
- <pre>lxc exec first -- free -m</pre>
- </p>
+ <p>And confirm that it's been applied with:
+ <pre>lxc exec first -- free -m</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#first-container" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#snapshots" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="snapshots">
- <h3>Snapshots</h3>
-
- <p>LXD supports snapshoting and restoring
- container snapshots.
- <br />
- Before making a snapshot, lets do some
- changes to the container, for example, updating it:
- <pre>lxc exec first -- apt-get update
- lxc exec first -- apt-get dist-upgrade -y
- lxc exec first -- apt-get autoremove --purge -y</pre>
- </p>
+ <div class="tab-content" id="snapshots">
+ <h3>Snapshots</h3>
+
+ <p>LXD supports snapshoting and restoring
+ container snapshots.
+ <br />
+ Before making a snapshot, lets do some
+ changes to the container, for example, updating it:
+ <pre>lxc exec first -- apt-get update
+ lxc exec first -- apt-get dist-upgrade -y
+ lxc exec first -- apt-get autoremove --purge -y</pre>
+ </p>
- <p>Now that the container is all updated and
- cleaned, let's make a snapshot called "clean":
- <pre>lxc snapshot first clean</pre>
- </p>
+ <p>Now that the container is all updated and
+ cleaned, let's make a snapshot called "clean":
+ <pre>lxc snapshot first clean</pre>
+ </p>
- <p>Let's break our container:
- <pre>lxc exec first -- rm -Rf /etc /usr</pre>
- </p>
+ <p>Let's break our container:
+ <pre>lxc exec first -- rm -Rf /etc /usr</pre>
+ </p>
- <p>Confirm the breakage with (then exit):
- <pre>lxc exec first -- bash</pre>
- </p>
+ <p>Confirm the breakage with (then exit):
+ <pre>lxc exec first -- bash</pre>
+ </p>
- <p>And restore everything to the snapshotted state:
- <pre>lxc restore first clean</pre>
- </p>
+ <p>And restore everything to the snapshotted state:
+ <pre>lxc restore first clean</pre>
+ </p>
- <p>And confirm everything's back to normal (then exit):
- <pre>lxc exec first -- bash</pre>
- </p>
+ <p>And confirm everything's back to normal (then exit):
+ <pre>lxc exec first -- bash</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#limiting-resources" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#creating-images" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="creating-images">
- <h3>Creating images</h3>
+ <div class="tab-content" id="creating-images">
+ <h3>Creating images</h3>
- <p>As your probably noticed earlier, LXD is
- image based, that is, all containers must be
- created from either a copy of an existing
- container or from an image.</p>
+ <p>As your probably noticed earlier, LXD is
+ image based, that is, all containers must be
+ created from either a copy of an existing
+ container or from an image.</p>
- <p>You can create new images from an existing
- container or a container snapshot.</p>
+ <p>You can create new images from an existing
+ container or a container snapshot.</p>
- <p>To publish our "clean" snapshot from earlier
- as a new image with a user friendly alias of
- "clean-ubuntu", run:
- <pre>lxc publish first/clean --alias clean-ubuntu</pre>
- </p>
+ <p>To publish our "clean" snapshot from earlier
+ as a new image with a user friendly alias of
+ "clean-ubuntu", run:
+ <pre>lxc publish first/clean --alias clean-ubuntu</pre>
+ </p>
- <p>At which point we won't need our "first"
- container, so just delete it with:
- <pre>lxc stop first
- lxc delete first</pre>
- </p>
+ <p>At which point we won't need our "first"
+ container, so just delete it with:
+ <pre>lxc stop first
+ lxc delete first</pre>
+ </p>
- <p>And lastly we can start a new container from
- our image with:
- <pre>lxc launch clean-ubuntu second</pre>
- </p>
+ <p>And lastly we can start a new container from
+ our image with:
+ <pre>lxc launch clean-ubuntu second</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#snapshots" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#container-files" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="container-files">
- <h3>Accessing files from the container</h3>
+ <div class="tab-content" id="container-files">
+ <h3>Accessing files from the container</h3>
- <p>To pull a file from the container you can use
- the "lxc file pull" command:
- <pre>lxc file pull second/etc/hosts .</pre>
- </p>
+ <p>To pull a file from the container you can use
+ the "lxc file pull" command:
+ <pre>lxc file pull second/etc/hosts .</pre>
+ </p>
- <p>Let's add an entry to it:
- <pre>echo "1.2.3.4 my-example" >> hosts</pre>
- </p>
+ <p>Let's add an entry to it:
+ <pre>echo "1.2.3.4 my-example" >> hosts</pre>
+ </p>
- <p>And push it back where it came from:
- <pre>lxc file push hosts second/etc/hosts</pre>
- </p>
+ <p>And push it back where it came from:
+ <pre>lxc file push hosts second/etc/hosts</pre>
+ </p>
- <p>You can also use this mechanism to access log files:
- <pre>lxc file pull second/var/log/syslog - | less</pre>
- </p>
+ <p>You can also use this mechanism to access log files:
+ <pre>lxc file pull second/var/log/syslog - | less</pre>
+ </p>
- <p>We won't be needing that container anymore,
- so stop and delete it with:
- <pre>lxc delete --force second</pre>
- </p>
+ <p>We won't be needing that container anymore,
+ so stop and delete it with:
+ <pre>lxc delete --force second</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#creating-images" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#image-server" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="image-server">
- <h3>Use a remote image server</h3>
+ <div class="tab-content" id="image-server">
+ <h3>Use a remote image server</h3>
- <p>The lxc client tool supports multiple
- "remotes", those remotes can be read-only
- image servers or other LXD hosts.</p>
+ <p>The lxc client tool supports multiple
+ "remotes", those remotes can be read-only
+ image servers or other LXD hosts.</p>
- <p>LXC upstream runs one such server at
- <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
- which serves a set of automatically generated
- images for various Linux distributions.
- </p>
+ <p>LXC upstream runs one such server at
+ <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
+ which serves a set of automatically generated
+ images for various Linux distributions.
+ </p>
- <p>It comes pre-added with default LXD but you
- can remove it or change it if you don't want it.
- </p>
+ <p>It comes pre-added with default LXD but you
+ can remove it or change it if you don't want it.
+ </p>
- <p>You can list the available images with:
- <pre>lxc image list images: | less</pre>
- </p>
+ <p>You can list the available images with:
+ <pre>lxc image list images: | less</pre>
+ </p>
- <p>And spawn a new Centos 7 container with:
- <pre>lxc launch images:centos/7 third</pre>
- </p>
+ <p>And spawn a new Centos 7 container with:
+ <pre>lxc launch images:centos/7 third</pre>
+ </p>
- <p>Confirm it's indeed Centos 7 with:
- <pre>lxc exec third -- cat /etc/redhat-release</pre>
- </p>
+ <p>Confirm it's indeed Centos 7 with:
+ <pre>lxc exec third -- cat /etc/redhat-release</pre>
+ </p>
- <p>And delete it:
- <pre>lxc delete -f third</pre>
- </p>
+ <p>And delete it:
+ <pre>lxc delete -f third</pre>
+ </p>
- <p>The list of all configured remotes can be
- obtained with:
- <pre>lxc remote list</pre>
- </p>
+ <p>The list of all configured remotes can be
+ obtained with:
+ <pre>lxc remote list</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#container-files" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#remote-lxd" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="remote-lxd">
- <h3>Interact with remote LXD servers</h3>
+ <div class="tab-content" id="remote-lxd">
+ <h3>Interact with remote LXD servers</h3>
- <p>For this step, you'll need a second demo
- session, so open a new one
- <a href="/lxd/try-it/" target="_blank">here</a></p>
+ <p>For this step, you'll need a second demo
+ session, so open a new one
+ <a href="/lxd/try-it/" target="_blank">here</a></p>
- <p>Copy/paste the "lxc remote add" command from
- the top of the page of that new session into
- the shell of your old session.
- <br />
- Then confirm the server fingerprint for the remote
- server.</p>
+ <p>Copy/paste the "lxc remote add" command from
+ the top of the page of that new session into
+ the shell of your old session.
+ <br />
+ Then confirm the server fingerprint for the remote
+ server.</p>
- <p>Note that it may take a few seconds for the
- new LXD daemon to listen to the network, just
- retry the command until it answers.</p>
+ <p>Note that it may take a few seconds for the
+ new LXD daemon to listen to the network, just
+ retry the command until it answers.</p>
- <p>At this point you can list the remote
- containers with: <pre>lxc list tryit:</pre></p>
+ <p>At this point you can list the remote
+ containers with: <pre>lxc list tryit:</pre></p>
- <p>And its images with:
- <pre>lxc image list tryit:</pre>
- </p>
+ <p>And its images with:
+ <pre>lxc image list tryit:</pre>
+ </p>
- <p>Now, let's start a new container on the remote
- LXD using the local image we created earlier.
- <pre>lxc launch clean-ubuntu tryit:fourth</pre>
- </p>
+ <p>Now, let's start a new container on the remote
+ LXD using the local image we created earlier.
+ <pre>lxc launch clean-ubuntu tryit:fourth</pre>
+ </p>
- <p>You now have a container called "fourth"
- running on the remote host "tryit". You can
- spawn a shell inside it with (then exit):
- <pre>lxc exec tryit:fourth bash</pre>
- </p>
+ <p>You now have a container called "fourth"
+ running on the remote host "tryit". You can
+ spawn a shell inside it with (then exit):
+ <pre>lxc exec tryit:fourth bash</pre>
+ </p>
- <p>Now let's copy that container into a new one
- called "fifth":
- <pre>lxc copy tryit:fourth tryit:fifth</pre>
- </p>
+ <p>Now let's copy that container into a new one
+ called "fifth":
+ <pre>lxc copy tryit:fourth tryit:fifth</pre>
+ </p>
- <p>And just for fun, move it back to our local
- lxd while renaming it to "sixth":
- <pre>lxc move tryit:fifth sixth</pre>
- </p>
+ <p>And just for fun, move it back to our local
+ lxd while renaming it to "sixth":
+ <pre>lxc move tryit:fifth sixth</pre>
+ </p>
- <p>And confirm it's all still working (then exit):
- <pre>lxc start sixth
- lxc exec sixth -- bash</pre>
- </p>
+ <p>And confirm it's all still working (then exit):
+ <pre>lxc start sixth
+ lxc exec sixth -- bash</pre>
+ </p>
- <p>Then clean everything up:
- <pre>lxc delete -f sixth
- lxc delete -f tryit:fourth
- lxc image delete clean-ubuntu</pre>
- </p>
+ <p>Then clean everything up:
+ <pre>lxc delete -f sixth
+ lxc delete -f tryit:fourth
+ lxc image delete clean-ubuntu</pre>
+ </p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="active"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#remote-lxd" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#conclusion" class="p-button js-tab-button">Next</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
- <div class="tab-pane fade in" id="conclusion">
- <h3>Conclusion</h3>
+ <div class="tab-content" id="conclusion">
+ <h3>Conclusion</h3>
- <p>We hope this gave you a good introduction to
- LXD, its capabilities and how easy it is to
- use.</p>
+ <p>We hope this gave you a good introduction to
+ LXD, its capabilities and how easy it is to
+ use.</p>
- <p>You're welcome to use the demo service as
- long as you want to try LXD and play with the
- latest features.</p>
+ <p>You're welcome to use the demo service as
+ long as you want to try LXD and play with the
+ latest features.</p>
- <p>Enjoy!</p>
+ <p>Enjoy!</p>
- <nav aria-label="...">
- <ul class="pager">
- <li class="active"><a href="#" class="tabPrevious">Previous</a></li>
- <li class="disabled"><a href="#" class="tabNext">Next</a></li>
- </ul>
- </nav>
- </div>
+ <nav aria-label="...">
+ <ul class="p-inline-list u-align--center">
+ <li class="p-inline-list__item">
+ <a href="#image-server" class="p-button js-tab-button">Previous</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a href="#conclusion" class="p-button is--disabled" aria-disabled="true">Next</a>
+ </li>
+ </ul>
+ </nav>
</div>
</div>
</div>
@@ -488,58 +531,48 @@
</div>
</div>
- <div class="panel panel-danger" id="tryit_error_panel" style="display:none">
- <div class="panel-heading" id="tryit_error_panel_create" style="display:none">Unable to create a new container</div>
- <div class="panel-heading" id="tryit_error_panel_access" style="display:none">Unable to access the container</div>
-
- <div class="panel-body" id="tryit_error_full" style="display:none">
- The server is currently full, please try again in a few minutes.
-
- <br /><br />
-
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
-
- <div class="panel-body" id="tryit_error_quota" style="display:none">
- You have reached the maximum number of concurrent sessions,
- please wait for some to expire before starting more of them.
+ <div class="p-notification--negative" id="tryit_error_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status" id="tryit_error_panel_create" style="display:none">Unable to create a new container</span>
+ <span class="p-notification__status" id="tryit_error_panel_access" style="display:none">Unable to access the container</span>
- <br /><br />
+ <div class="panel-body" id="tryit_error_full" style="display:none">
+ <p>The server is currently full, please try again in a few minutes.</p>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
+ <p><button class="p-button tryit_goback" type="button">
+ Start over
+ </button></p>
+ </div>
- <div class="panel-body" id="tryit_error_banned" style="display:none">
- You have been banned from this service due to a failure to
- respect the terms of service.
- </div>
+ <div class="panel-body" id="tryit_error_quota" style="display:none">
+ <p>You have reached the maximum number of concurrent sessions,
+ please wait for some to expire before starting more of them.</p>
- <div class="panel-body" id="tryit_error_unknown" style="display:none">
- An unknown error occured. Please try again in a few minutes.
+ <p><button class="p-button tryit_goback" type="button">
+ Start over
+ </button></p>
+ </div>
- <br /><br />
+ <div class="panel-body" id="tryit_error_banned" style="display:none">
+ <p>You have been banned from this service due to a failure to
+ respect the terms of service.</p>
+ </div>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
- </div>
+ <div class="panel-body" id="tryit_error_unknown" style="display:none">
+ <p>An unknown error occured. Please try again in a few minutes.</p>
- <div class="panel-body" id="tryit_error_missing" style="display:none">
- The container you're trying to connect to doesn't exist anymore.
+ <p><button class="p-button tryit_goback" type="button">
+ Start over
+ </button></p>
+ </div>
- <br /><br />
+ <div class="panel-body" id="tryit_error_missing" style="display:none">
+ <p>The container you're trying to connect to doesn't exist anymore.</p>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- Start over
- </button>
+ <p><button class="p-button tryit_goback" type="button">
+ Start over
+ </button></p>
+ </div>
</div>
</div>
</div>
diff --git a/generate b/generate
index 7412eed..f416253 100755
--- a/generate
+++ b/generate
@@ -219,6 +219,7 @@ def gen_page(entry, override, prefix, **variables):
template = "page.tpl.html"
if item['generator'] == "html":
+ template = "html.tpl.html"
with open(content_path(item['meta']['input']), "r") as fd:
content = fd.read()
elif item['generator'] == "markdown":
diff --git a/static/css/local.css b/static/css/local.css
index ac931e6..75b91b4 100644
--- a/static/css/local.css
+++ b/static/css/local.css
@@ -26,7 +26,6 @@ h3:hover a.headerlink {
border-top: 1px solid #999;
}
-<<<<<<< 50e47ddbf10d8e51e2cfc8a11f556aca69dd7a3a
.symbol {
display: inline-block;
border-radius: 50%;
@@ -41,12 +40,16 @@ h3:hover a.headerlink {
.symbol-filled {
background-color: black;
-=======
+}
+
.dropdown-submenu:hover .dropdown-menu {
display: block;
}
-.dropdown-submenu .dropdown-menu {
+
+ at media only screen and (min-width: 768px) {
+
+ .dropdown-submenu .dropdown-menu {
display: none;
position: absolute;
left: 90%;
@@ -55,14 +58,560 @@ h3:hover a.headerlink {
border: 1px solid #cdcdcd;
border-radius: 10px;
box-shadow: 0 2px 2px -1px #cdcdcd;
+ width: 200px;
+ padding-top: .3rem;
+ padding-bottom: .8rem;
+ }
+
+ .dropdown-submenu .dropdown-menu.columns {
+ width: 300px;
+ }
+
+ .dropdown-submenu .dropdown-menu.columns li {
+ float: left;
+ width: 140px;
+ margin-top: 0;
+ }
+ .dropdown-menu::after {
+ transform: rotate(-90deg);
+ left: -48px !important;
+ width: 90px !important;
+ top: 0 !important;
+ }
}
- at media only screen and (min-width: 768px) {
- .dropdown-menu::after {
- transform: rotate(-90deg);
- left: -48px !important;
- width: 90px !important;
- top: 0 !important;
- }
->>>>>>> Fix nested navigation
+html {
+ overflow-x: hidden !important;
+}
+
+
+/* Navigation */
+.p-navigation::after {
+ clear: both;
+ content: '';
+ display: block;
+}
+
+.p-navigation {
+ background-color: #e95420;
+ border-bottom: 1px solid transparent;
+ color: #f7f7f7;
+ margin-top: 0;
+ position: relative;
+ width: 100%;
+ font-weight: 400;
+ margin-bottom: 0;
+}
+.p-navigation .row {
+ padding: 0;
+}
+ at media (max-width: 768px) {
+ .p-navigation .p-navigation__banner {
+ overflow: hidden;
+ position: relative;
+ }
+}
+.p-navigation .p-navigation__toggle--open,
+.p-navigation .p-navigation__toggle--close,
+.p-navigation .p-navigation__link {
+ color: #f7f7f7;
+}
+.p-navigation .p-navigation__toggle--open:hover,
+.p-navigation .p-navigation__toggle--close:hover,
+.p-navigation .p-navigation__link:hover {
+ border-bottom: 0;
+ text-decoration: underline;
+}
+.p-navigation .p-navigation__toggle--open:visited,
+.p-navigation .p-navigation__toggle--close:visited,
+.p-navigation .p-navigation__link:visited {
+ color: #f7f7f7;
+}
+.p-navigation .p-navigation__toggle--close {
+ display: none;
+}
+.p-navigation .p-navigation__toggle--open,
+.p-navigation .p-navigation__toggle--close {
+ margin: 0;
+ position: absolute;
+ right: 1rem;
+ top: calc(50% - .75rem);
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__toggle--open,
+ .p-navigation .p-navigation__toggle--close {
+ display: none;
+ }
+}
+.p-navigation .p-navigation__logo {
+ font-size: 1.375rem;
+ font-weight: 300;
+ line-height: 1.364;
+ -webkit-box-align: center;
+ -webkit-align-items: center;
+ -ms-flex-align: center;
+ align-items: center;
+ display: -webkit-box;
+ display: -webkit-flex;
+ display: -ms-flexbox;
+ display: flex;
+ float: left;
+ margin: 0.75rem 0.5rem;
+}
+ at media only screen and (min-width: 1030px) {
+ .p-navigation .p-navigation__logo {
+ font-size: 1.5rem;
+ line-height: 1.25;
+ }
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__logo {
+ margin: 0.5rem 1.25rem;
+ }
+}
+.p-navigation .p-navigation__image {
+ float: left;
+ height: 2rem;
+}
+.p-navigation .p-navigation__link {
+ border-bottom: 0;
+ display: block;
+ margin-top: 0;
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__link {
+ display: block;
+ float: left;
+ width: auto;
+ }
+}
+.p-navigation .p-navigation__link,
+.p-navigation .p-navigation__link > a {
+ border-bottom: 0;
+ display: block;
+}
+.p-navigation .p-navigation__link:hover,
+.p-navigation .p-navigation__link > a:hover {
+ text-decoration: none;
+}
+.p-navigation .p-navigation__link:last-child {
+ margin-bottom: 0;
+}
+.p-navigation .p-navigation__links {
+ background-color: #cdcdcd;
+ clear: both;
+ margin: 0;
+ padding: 0;
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__links {
+ background-color: transparent;
+ clear: none;
+ float: left;
+ }
+}
+.p-navigation .p-navigation__links .p-navigation__link {
+ border-left: 1px solid #cdcdcd;
+}
+ at media (max-width: 768px) {
+ .p-navigation .p-navigation__links .p-navigation__link {
+ background-color: #f7f7f7;
+ border-left: 0;
+ border-top: 1px solid #cdcdcd;
+ color: #111;
+ text-align: left;
+ }
+ .p-navigation .p-navigation__links .p-navigation__link:last-child {
+ border-bottom: 1px solid #cdcdcd;
+ }
+}
+.p-navigation .p-navigation__links .p-navigation__link > a,
+.p-navigation .p-navigation__links > a {
+ color: #111;
+ font-size: .875rem;
+ padding: 0.84375rem 0.5rem;
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__links .p-navigation__link > a,
+ .p-navigation .p-navigation__links > a {
+ color: #f7f7f7;
+ padding-left: 1.25rem;
+ padding-right: 1.25rem;
+ }
+}
+
+.p-navigation .p-navigation__links:last-of-type {
+ border-color: #ee784e;
+}
+ at media (max-width: 769px) {
+ .p-navigation .p-navigation__links {
+ border-right: 1px solid #cdcdcd;
+ }
+}
+ at media (max-width: 768px) {
+ .p-navigation .p-navigation__links:last-of-type {
+ border-bottom: 0;
+ border-right: 0;
+ }
+}
+.p-navigation .p-navigation__nav {
+ display: none;
+ margin-top: 0;
+}
+ at media (min-width: 769px) {
+ .p-navigation .p-navigation__nav {
+ display: block;
+ }
+}
+.p-navigation:target .p-navigation__toggle--open {
+ display: none;
+}
+ at media (max-width: 768px) {
+ .p-navigation:target .p-navigation__toggle--close {
+ display: inline-block;
+ }
+}
+.p-navigation:target .p-navigation__nav {
+ display: block;
+}
+ at media (max-width: 768px) {
+ .p-navigation {
+ border-bottom: 1px solid #f7f7f7;
+ font-weight: 300;
+ }
+}
+ at media (max-width: 768px) {
+ .p-navigation .p-navigation__toggle--open,
+ .p-navigation .p-navigation__toggle--close {
+ top: .875rem;
+ }
+}
+.p-navigation__logo {
+ margin: 0;
+ padding: 0;
+}
+ at media (min-width: 768px) and (max-width: 1030px) {
+ .p-navigation__logo {
+ margin-left: 0;
+ padding-left: 0;
+ }
+}
+ at media (min-width: 1030px) {
+ .p-navigation__row {
+ position: relative;
+ }
+}
+.p-navigation .p-navigation__links .p-navigation__link {
+ border-right: 1px solid #cdcdcd;
+ font-size: .875rem;
+ padding: 0;
+ position: relative;
+}
+ at media (min-width: 768px) {
+ .p-navigation .p-navigation__links .p-navigation__link {
+ border-color: #ee784e;
+ border-right: 0;
+ }
+}
+.p-navigation .p-navigation__links .p-navigation__link:hover {
+ cursor: pointer;
+}
+ at media (max-width: 767px) {
+ .p-navigation .p-navigation__links .p-navigation__link > a {
+ padding: 0.75rem 1rem;
+ }
+ .p-navigation .p-navigation__links .p-navigation__link > a.is-active {
+ background-color: #cdcdcd;
+ }
+}
+ at media (min-width: 768px) {
+ .p-navigation .p-navigation__links .p-navigation__link > a {
+ display: inline-block;
+ padding: 1rem 0.75rem;
+ }
+ .p-navigation .p-navigation__links .p-navigation__link > a.is-active {
+ background-color: #c34113;
+ }
+ .p-navigation .p-navigation__links .p-navigation__link:hover {
+ background-color: #ee784e;
+ }
+}
+
+.p-navigation .p-navigation__logo {
+ margin: 0.75rem 0.75rem 0.5rem 1rem;
+ padding: 0;
+}
+
+.nav-secondary .p-inline-list__link {
+ display: inline-block;
+}
+ at media (min-width: 768px) and (max-width: 1030px) {
+ .nav-secondary {
+ border-top: 1px solid #cdcdcd;
+ white-space: nowrap;
+ }
+}
+ at media (max-width: 767px) {
+ .nav-secondary__row.row {
+ padding: 0;
+ }
+}
+ at media (min-width: 768px) {
+ .nav-secondary__row {
+ padding: 0 0.75rem;
+ }
+}
+
+.nav-secondary .p-inline-list__link,
+.nav-secondary .p-breadcrumbs__link{
+ font-size: .875rem;
+ font-weight: 300;
}
+ at media (max-width: 767px) {
+ .nav-secondary {
+ background: #fff;
+ }
+ .nav-secondary .p-breadcrumbs {
+ position: relative;
+ left: 50%;
+ -webkit-transform: translate(-50%, 0);
+ -ms-transform: translate(-50%, 0);
+ transform: translate(-50%, 0);
+ width: 100vw;
+ border-bottom: 1px solid #cdcdcd;
+ overflow-x: hidden;
+ padding: 0 20px;
+ }
+ .nav-secondary .p-breadcrumbs__item {
+ left: 50%;
+ margin-left: 0;
+ position: relative;
+ -webkit-transform: translate(-50%, 0);
+ -ms-transform: translate(-50%, 0);
+ transform: translate(-50%, 0);
+ width: 100%;
+ padding: .5rem 0;
+ }
+ .nav-secondary .p-breadcrumbs__link {
+ border-bottom: 1px solid #cdcdcd;
+ color: #111;
+ display: inline-block;
+ margin-bottom: 0.5rem;
+ padding: 0.75rem 1rem;
+ width: 100%;
+ }
+ .nav-secondary__menu {
+ width: 100%;
+ }
+ .nav-secondary__menu .p-inline-list__item {
+ float: left;
+ margin-right: 0;
+ margin-top: 0;
+ padding-left: 0.5rem;
+ width: 50%;
+ }
+ .nav-secondary__menu .p-inline-list__item .is-active {
+ font-weight: bold;
+ }
+ .nav-secondary__menu .p-inline-list__link {
+ color: #000;
+ display: inline-block;
+ padding: 0.5rem;
+ }
+
+ .p-breadcrumbs__item:not(:first-of-type):before {
+ top: .5rem;
+ }
+}
+.nav-secondary__menu {
+ display: inline-block;
+ margin-top: 0;
+ position: relative;
+}
+ at media (min-width: 768px) {
+ .nav-secondary__menu {
+ margin-left: 1.5rem;
+ vertical-align: top;
+ }
+}
+.nav-secondary a {
+ color: #111;
+}
+.nav-secondary a.is-active {
+ color: #e95420;
+}
+ at media (min-width: 768px) {
+ .nav-secondary {
+ position: relative;
+ left: 50%;
+ -webkit-transform: translate(-50%, 0);
+ -ms-transform: translate(-50%, 0);
+ transform: translate(-50%, 0);
+ background: #f7f7f7;
+ border-bottom: 1px solid #cdcdcd;
+ padding: 0.5rem 0 0.75rem;
+ white-space: nowrap;
+ }
+ .nav-secondary .p-breadcrumbs__item {
+ margin-bottom: 0;
+ }
+ .nav-secondary__menu::before {
+ color: #666;
+ content: '\203A';
+ font-weight: 400;
+ left: -0.75rem;
+ position: absolute;
+ top: 0;
+ }
+ .nav-secondary .p-breadcrumbs__link {
+ color: #666;
+ }
+}
+ at media (min-width: 768px) {
+ .nav-secondary .p-breadcrumbs__link + .second-level-nav {
+ position: relative;
+ }
+ .nav-secondary .p-breadcrumbs__link + .second-level-nav::before {
+ color: #666;
+ content: '\203A';
+ font-weight: 400;
+ left: -0.5rem;
+ position: absolute;
+ top: 0;
+ }
+}
+
+ at media (min-width: 1030px) {
+ .nav-secondary__row {
+ padding: 0 0.75rem;
+ }
+}
+.nav-secondary .p-navigation__row {
+ padding-left: 0.5rem;
+ padding-right: 0.5rem;
+}
+
+.hover-menu {
+ background: #f7f7f7;
+ border: 1px solid #cdcdcd;
+ display: none;
+ float: none;
+ margin: 0;
+ padding: 0.5rem 0 1rem;
+}
+ at media (min-width: 769px) {
+ .p-navigation__link:hover .hover-menu {
+ display: block;
+ }
+ .p-navigation__link:hover .hover-menu .p-inline-list__item {
+ display: block;
+ }
+
+ .p-navigation .p-navigation__nav ul li:hover ul::after {
+ background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAYAAAD5nd/tAAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH3QYODgYVPPJJpQAAAT9JREFUKM+dkD9IAnEUx7+/IkVxFaxoKYxIWhqKwJw0JAJ315Yac8+1tUFo6HCp34XRdRp11z+J4BzckqShPzdEQ5G/EhPO6V5Tcg3G0QcePHjvffjygB4oXAIApFMxyPlcWM7nwulU7NfMNQqXGABsZNcCCpcKtapBtapBCpcK2fXlAAAcy3vMlUxTdgEAO9ubybPiPjWFoE6nQ5ZlUfNDULl0RAdSPuncddL30+gnCgOAlngLaocyn4nG9fmFJXj9fhARAMDr82MuEcfk7LSuFQu8DTvovO1SuTxlAKCqPFO5Ov/6FIIsy/qzROOdrst6S1V5xunomo0LrT4yOh4JDg6BMXfvIdvGs/mExutLPZpYnAIAdmNUVuwBbI1NRODxePEf2u0WHu9u4ev3rTLTfKBQaNh1qp5piWCa9/gGBheo3r6AmYcAAAAASUVORK5CYII=") 1.5rem bottom no-repeat;
+ content: '';
+ display: block;
+ height: 0.5rem;
+ left: 0;
+ position: absolute;
+ top: -0.5rem;
+ width: 200px;
+ z-index: 999;
+ }
+ .hover-menu {
+ background: #f7f7f7;
+ border: 1px solid #cdcdcd;
+ border-radius: 10px;
+ box-shadow: 0 2px 2px -1px #cdcdcd;
+ display: none;
+ float: none;
+ left: 0;
+ margin: 0;
+ padding: 0.5rem 0 1rem;
+ position: absolute;
+ top: 58px;
+ width: 200px;
+ z-index: 1;
+ }
+ .hover-menu::before {
+ display: none;
+ }
+ .hover-menu li {
+ font-size: .875rem;
+ padding: 0.5rem 0.75rem 0 0.75rem;
+ }
+ .hover-menu li:last-child {
+ padding-bottom: 0;
+ }
+ .hover-menu a {
+ color: #111 !important;
+ }
+}
+ at media (max-width: 767px) {
+ .p-navigation__links > .p-navigation__link:hover .hover-menu {
+ display: block;
+ }
+
+ .hover-menu li {
+ padding: .25rem 1rem;
+ }
+}
+
+.p-breadcrumbs__link + .second-level-nav, .p-breadcrumbs__link + .second-level-nav .p-breadcrumbs__link {
+ display: inline-block;
+ margin-bottom: 0;
+ padding-left: 0;
+}
+ at media (max-width: 767px) {
+ .p-breadcrumbs__link + .second-level-nav, .p-breadcrumbs__link + .second-level-nav .p-breadcrumbs__link {
+ width: 100%;
+ }
+}
+.second-level-nav .p-breadcrumbs__link {
+ border-bottom: 0;
+ padding-bottom: 0;
+ padding-top: 0;
+}
+
+.dropdown-backdrop {
+ display: none;
+}
+
+/* Notifications */
+.p-notification__body {
+ margin-top: 1rem;
+ text-align: left;
+}
+
+p:empty {
+ display: none;
+}
+
+/* Tabs */
+.tab-content {
+ display: none;
+}
+
+.tab-content:target {
+ display: block;
+}
+
+/* Terminal */
+#tryit_console * {
+ margin-top: 0;
+}
+
+#tryit_console_measurement {
+ color: white;
+ display: block;
+ float: left;
+ border-color: black;
+ border-style: solid;
+ border-width: 5px 5px 5px 5px;
+ position: absolute;
+ top: -1000px;
+}
+
+.terminal {
+ width: 100%;
+}
\ No newline at end of file
diff --git a/static/js/tryit.js b/static/js/tryit.js
index 5c20782..9d80a4a 100644
--- a/static/js/tryit.js
+++ b/static/js/tryit.js
@@ -235,7 +235,7 @@ $(document).ready(function() {
$('#tryit_examples_panel').css("display", "inherit");
tryit_console = data.id;
- window.history.pushState("", "", "?id="+tryit_console);
+ window.history.pushState("", "", "?id="+tryit_console+"#introduction");
setupConsole(tryit_console);
},
error: function(data) {
diff --git a/templates/common/base.tpl.html b/templates/common/base.tpl.html
index 2d10580..f3c403c 100644
--- a/templates/common/base.tpl.html
+++ b/templates/common/base.tpl.html
@@ -11,8 +11,7 @@
{% else %}
<title>Linux Containers</title>
{% endif %}
-
- <link rel="stylesheet" href="https://www.ubuntu.com/static/css/styles.css" />
+ <link rel="stylesheet" href="https://assets.ubuntu.com/v1/vanilla-framework-version-1.6.1.min.css" />
<link href="/static/css/local.css" rel="stylesheet"/>
<link href="/static/css/pygments.css" rel="stylesheet"/>
diff --git a/templates/common/header.tpl.html b/templates/common/header.tpl.html
index 0ae4d7d..20645db 100644
--- a/templates/common/header.tpl.html
+++ b/templates/common/header.tpl.html
@@ -1,8 +1,10 @@
-<div class="p-navigation">
+<div id="navigation" class="p-navigation">
<div class="row">
<div class="p-navigation__logo">
<a class="p-navigation__link" href="/">Linux Containers</a>
</div>
+ <a href="#navigation" class="p-navigation__toggle--open" title="menu">Menu</a>
+ <a href="#navigation-closed" class="p-navigation__toggle--close" title="close menu">Close menu</a>
<nav class="p-navigation__nav">
<span class="u-off-screen">
@@ -42,7 +44,7 @@
{% endif %}
{% else %}
{% if page_menu[1] == sub_entry[1] %}
- <li class="is-active">
+ <li class="is-active dropdown-submenu">
{% else %}
<li class="dropdown-submenu">
{% endif %}
diff --git a/templates/downloads.tpl.html b/templates/downloads.tpl.html
index 408d8f2..8b193d1 100644
--- a/templates/downloads.tpl.html
+++ b/templates/downloads.tpl.html
@@ -2,6 +2,7 @@
{% block content %}
<div class="row">
<div class="p-strip">
+ <div class="col-8">
{{ content }}
{% if downloads %}
@@ -21,6 +22,7 @@
{% endfor %}
</table>
{% endif %}
-</div>
+ </div>
+ </div>
</div>
{% endblock %}
diff --git a/templates/html.tpl.html b/templates/html.tpl.html
new file mode 100644
index 0000000..10ae289
--- /dev/null
+++ b/templates/html.tpl.html
@@ -0,0 +1,4 @@
+{% extends "common/base.tpl.html" %}
+{% block content %}
+ {{ content }}
+{% endblock %}
diff --git a/templates/markdown-page.tpl.html b/templates/markdown-page.tpl.html
index fcbee1a..1142629 100644
--- a/templates/markdown-page.tpl.html
+++ b/templates/markdown-page.tpl.html
@@ -2,7 +2,9 @@
{% block content %}
<div class="row">
<div class="p-strip">
- {{ content }}
+ <div class="col-8">
+ {{ content }}
+ </div>
</div>
</div>
{% endblock %}
diff --git a/templates/page.tpl.html b/templates/page.tpl.html
index 10ae289..4388b54 100644
--- a/templates/page.tpl.html
+++ b/templates/page.tpl.html
@@ -1,4 +1,10 @@
{% extends "common/base.tpl.html" %}
{% block content %}
- {{ content }}
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ {{ content }}
+ </div>
+ </div>
+</div>
{% endblock %}
From d616dc0d401a31593ae8d3fbfa84dd16e1d0f672 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Tue, 31 Oct 2017 14:20:00 +0000
Subject: [PATCH 4/8] Add fixes for the languages menu
---
static/css/local.css | 12 ++++++++++++
templates/common/header.tpl.html | 38 ++++++++++++++++++++------------------
2 files changed, 32 insertions(+), 18 deletions(-)
diff --git a/static/css/local.css b/static/css/local.css
index 75b91b4..bcdcc92 100644
--- a/static/css/local.css
+++ b/static/css/local.css
@@ -499,6 +499,7 @@ html {
margin: 0;
padding: 0.5rem 0 1rem;
}
+
@media (min-width: 769px) {
.p-navigation__link:hover .hover-menu {
display: block;
@@ -546,6 +547,17 @@ html {
.hover-menu a {
color: #111 !important;
}
+ .hover-menu .is-active a {
+ color: #e95420 !important;
+ }
+ .u-float-right .hover-menu {
+ right: 0;
+ left: auto;
+ text-align: right;
+ }
+ .p-navigation .p-navigation__nav.u-float-right ul li:hover ul::after {
+ background-position-x: 90%;
+ }
}
@media (max-width: 767px) {
.p-navigation__links > .p-navigation__link:hover .hover-menu {
diff --git a/templates/common/header.tpl.html b/templates/common/header.tpl.html
index 20645db..639d403 100644
--- a/templates/common/header.tpl.html
+++ b/templates/common/header.tpl.html
@@ -77,28 +77,30 @@
</li>
{% endif %}
{% endfor %}
- </ul>
+ </ul>
{% endif %}
-{% if not languages %}
- <ul class="u-align--right">
- <li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">{{ page_language[2] }} <span class="caret"></span></a>
- <ul class="dropdown-menu" role="menu">
- {% for language in languages %}
- {% if page_language[0] == language[0] %}
- <li class="active"><a href="#">{{ language[1] }}</a></li>
- {% else %}
- {% if language[0] %}
- <li><a href="/{{ language[0] }}{{ page_raw_path }}">{{ language[1] }}</a></li>
+{% if languages %}
+ <nav class="p-navigation__nav u-float-right">
+ <ul class="p-navigation__links">
+ <li class="p-navigation__link">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">{{ page_language[2] }} <span class="caret"></span></a>
+ <ul class="hover-menu" role="menu">
+ {% for language in languages %}
+ {% if page_language[0] == language[0] %}
+ <li class="is-active"><a href="#">{{ language[1] }}</a></li>
{% else %}
- <li><a href="{{ page_raw_path }}">{{ language[1] }}</a></li>
+ {% if language[0] %}
+ <li><a href="/{{ language[0] }}{{ page_raw_path }}">{{ language[1] }}</a></li>
+ {% else %}
+ <li><a href="{{ page_raw_path }}">{{ language[1] }}</a></li>
+ {% endif %}
{% endif %}
- {% endif %}
- {% endfor %}
- </ul>
- </li>
- </ul>
+ {% endfor %}
+ </ul>
+ </li>
+ </ul>
+ </nav>
{% endif %}
</div>
</div>
From 8c31b64a87b81bfb97e816ac2cb47d3dcc100286 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Wed, 1 Nov 2017 09:06:33 +0000
Subject: [PATCH 5/8] Update all homepages and footers
---
content/index.fr.html | 139 ++++++++++---------
content/index.html | 160 +++++++++++----------
content/index.ja.html | 270 +++++++++++++++++++-----------------
content/index.ko.html | 137 +++++++++---------
content/index.ru.html | 227 ++++++++++++++++--------------
templates/common/footer.fr.tpl.html | 25 ++--
templates/common/footer.ja.tpl.html | 25 ++--
templates/common/footer.ko.tpl.html | 25 ++--
templates/common/footer.ru.tpl.html | 26 ++--
templates/common/footer.tpl.html | 32 ++---
10 files changed, 574 insertions(+), 492 deletions(-)
diff --git a/content/index.fr.html b/content/index.fr.html
index 4fcc2e8..19a9363 100644
--- a/content/index.fr.html
+++ b/content/index.fr.html
@@ -1,81 +1,94 @@
-<h2>LinuxContainers.org <span class="text-muted">Infrastructure pour projets de conteneurs.</span></h2>
-<div class="large_content">
- <p><img src="/static/img/containers.png"
- alt="logo"/>
- linuxcontainers.org est le projet parent de LXC, LXD, LXCFS et
- CGManager.</p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>Infrastructure pour projets de conteneurs.</h1>
+ <p>linuxcontainers.org est le projet parent de LXC, LXD, LXCFS et
+ CGManager.</p>
- <p>L'objectif est d'offrir un environnement neutre, non influencé par des
- distributions ou fournisseurs, permettant le développement des technologies
- liées aux conteneurs Linux.</p>
+ <p>L'objectif est d'offrir un environnement neutre, non influencé par des
+ distributions ou fournisseurs, permettant le développement des technologies
+ liées aux conteneurs Linux.</p>
- <p>Ce projet se concentre sur les conteneurs systèmes. Ceux-ci
- offrent un environnement aussi proche que possible de celui
- d'une machine virtuelle, mais sans le surcoût associé à l'utilisation
- d'un noyau séparé ou à la simulation de matériel.</p>
+ <p>Ce projet se concentre sur les conteneurs systèmes. Ceux-ci
+ offrent un environnement aussi proche que possible de celui
+ d'une machine virtuelle, mais sans le surcoût associé à l'utilisation
+ d'un noyau séparé ou à la simulation de matériel.</p>
- <p>Tout ceci est possible grâce aux fonctionalités de sécurité du
- noyau telles que les "namespaces", le contrôle d'accès obligatoire (MAC)
- et les groupes de contrôle (CGroups).</p>
+ <p>Tout ceci est possible grâce aux fonctionalités de sécurité du
+ noyau telles que les "namespaces", le contrôle d'accès obligatoire (MAC)
+ et les groupes de contrôle (CGroups).</p>
+ </div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
-<hr/>
-<h2>Projets. <span class="text-muted">Les choses intéressantes.</span></h2>
-<div class="row">
- <div class="col-md-4">
- <h3>LXC</h3>
- <p>LXC est l'ensemble bien connu d'outils, modèles, bibliothèque et
- connecteurs pour différents langages. LXC est bas niveau,
- très flexible et couvre à peu près toutes les technologies de
- confinement supportées par le noyau.
- <p>LXC est prêt pour la production. La version 1.0 est supportée
- pour 5 ans (jusqu'en avril 2019) avec des mises à jour de sécurité et
- correctifs .</p>
- <p><a class="btn btn-primary" href="/fr/lxc/introduction/" role="button">Plus d'information »</a></p>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>Projets. Les choses intéressantes.</h2>
+ </div>
+ </div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>LXC est l'ensemble bien connu d'outils, modèles, bibliothèque et
+ connecteurs pour différents langages. LXC est bas niveau,
+ très flexible et couvre à peu près toutes les technologies de
+ confinement supportées par le noyau.
+ <p>LXC est prêt pour la production. La version 1.0 est supportée
+ pour 5 ans (jusqu'en avril 2019) avec des mises à jour de sécurité et
+ correctifs .</p>
+ <p><a class="p-button" href="/fr/lxc/introduction/" role="button">Plus d'information</a></p>
</div>
- <div class="col-md-4">
- <h3>LXD</h3>
- <p>LXD est la nouvelle expérience LXC avec une seule commande
- intuitive pour contrôler tous vos conteneurs. Les conteneurs
- sont gérés par le réseau de façon complètement transparente
- grâce à une interface REST. Il marche aussi à grande échelle,
- s'intégrant avec OpenStack.</p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>LXD est la nouvelle expérience LXC avec une seule commande
+ intuitive pour contrôler tous vos conteneurs. Les conteneurs
+ sont gérés par le réseau de façon complètement transparente
+ grâce à une interface REST. Il marche aussi à grande échelle,
+ s'intégrant avec OpenStack.</p>
- <p>LXD a été annoncé en début Novembre 2014 et est en
- développement actif.</p>
+ <p>LXD a été annoncé en début Novembre 2014 et est en
+ développement actif.</p>
- <p><a class="btn btn-primary" href="/fr/lxd/introduction/" role="button">Plus d'information »</a></p>
+ <p><a class="p-button" href="/fr/lxd/introduction/" role="button">Plus d'information</a></p>
</div>
- <div class="col-md-4">
- <h3>CGManager</h3>
- <p>CGManager est notre gestionnaire de cgroup. Son but est de
- permettre aux conteneurs imbriqués de créer et gérer leurs
- cgroups à travers une interface D-Bus.</p>
+ <div class="p-card col-4">
+ <h3>CGManager</h3>
+ <p>CGManager est notre gestionnaire de cgroup. Son but est de
+ permettre aux conteneurs imbriqués de créer et gérer leurs
+ cgroups à travers une interface D-Bus.</p>
- <p>CGManager a fait ses débuts en avril 2014 où il a été intégré
- avec LXC par Ubuntu. Depuis, il a rejoint d'autres
- distributions leur permettant ainsi d'offrir des conteneurs
- non-privilégiés fonctionnels.</p>
+ <p>CGManager a fait ses débuts en avril 2014 où il a été intégré
+ avec LXC par Ubuntu. Depuis, il a rejoint d'autres
+ distributions leur permettant ainsi d'offrir des conteneurs
+ non-privilégiés fonctionnels.</p>
- <p><a class="btn btn-primary" href="/fr/cgmanager/introduction/" role="button">Plus d'information »</a></p>
+ <p><a class="p-button" href="/fr/cgmanager/introduction/" role="button">Plus d'information</a></p>
</div>
+ </div>
+</div>
- <div class="col-md-6">
- <h3>LXCFS</h3>
- <p>Système de fichier (FUSE) offrant deux fonctionnalités principales:
- <ul>
- <li>Remplacement pour cpuinfo, meminfo, stat et uptime.</li>
- <li>Une vue compatible avec cgroupfs permettant les écritures non-privilégiées.</li>
- </ul>
- </p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ <h3>LXCFS</h3>
+ <p>Système de fichier (FUSE) offrant deux fonctionnalités principales:
+ <ul>
+ <li>Remplacement pour cpuinfo, meminfo, stat et uptime.</li>
+ <li>Une vue compatible avec cgroupfs permettant les écritures non-privilégiées.</li>
+ </ul>
+ </p>
- <p>Son but est de contourner les limites des systèmes de
- fichiers procfs, sysfs et cgroupfs par la mise à disposition
- de fichiers correspondant à ce que l'utilisateur s'attend à
- voir dans un conteneur complet (système).</p>
+ <p>Son but est de contourner les limites des systèmes de
+ fichiers procfs, sysfs et cgroupfs par la mise à disposition
+ de fichiers correspondant à ce que l'utilisateur s'attend à
+ voir dans un conteneur complet (système).</p>
- <p><a class="btn btn-primary" href="/fr/lxcfs/introduction/" role="button">Plus d'information »</a></p>
+ <p><a class="p-button" href="/fr/lxcfs/introduction/" role="button">Plus d'information </a></p>
</div>
-</div>
+ </div>
diff --git a/content/index.html b/content/index.html
index a41f05c..35feca1 100644
--- a/content/index.html
+++ b/content/index.html
@@ -1,104 +1,100 @@
<div class="p-strip">
- <div class="row">
- <div class="col-8 suffix-1">
- <h1>Infrastructure for container projects.</h1>
- <p>linuxcontainers.org is the umbrella project behind LXC,
- LXD and LXCFS.</p>
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>Infrastructure for container projects.</h1>
+ <p>linuxcontainers.org is the umbrella project behind LXC,
+ LXD and LXCFS.</p>
- <p>The goal is to offer a distro and vendor neutral environment
- for the development of Linux container technologies.</p>
+ <p>The goal is to offer a distro and vendor neutral environment
+ for the development of Linux container technologies.</p>
- <p>Our main focus is system containers. That is, containers which
- offer an environment as close as possible as the one you'd get from a
- VM but without the overhead that comes with running a separate
- kernel and simulating all the hardware.</p>
- </div>
- <div class="col-4">
- <img src="/static/img/containers.png" alt="" />
- </div>
+ <p>Our main focus is system containers. That is, containers which
+ offer an environment as close as possible as the one you'd get from a
+ VM but without the overhead that comes with running a separate
+ kernel and simulating all the hardware.</p>
</div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
-<div class="p-strip--light">
- <div class="row">
- <div class="col-8">
- <h2>Active projects</h2>
- </div>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>Active projects</h2>
+ </div>
+ </div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>LXC is the well known set of tools, templates,
+ library and language bindings. It's pretty low
+ level, very flexible and covers just about every
+ containment feature supported by the upstream
+ kernel.</p>
+ <p>LXC is production ready with LXC 1.0 getting 5
+ years of security updates and bugfixes
+ (until April 2019).</p>
+ <p><a class="p-button" href="/lxc/introduction/" role="button">Learn more</a></p>
</div>
- <div class="row u-equal-height">
- <div class="p-card col-4">
- <h3>LXC</h3>
- <p>LXC is the well known set of tools, templates,
- library and language bindings. It's pretty low
- level, very flexible and covers just about every
- containment feature supported by the upstream
- kernel.</p>
- <p>LXC is production ready with LXC 1.0 getting 5
- years of security updates and bugfixes
- (until April 2019).</p>
- <p><a class="p-button" href="/lxc/introduction/" role="button">Learn more</a></p>
- </div>
- <div class="p-card col-4">
- <h3>LXD</h3>
- <p>LXD is the new LXC experience. It offers a
- completely fresh and intuitive user experience
- with a single command line tool to manage your
- containers. Containers can be managed over the
- network in a transparent way through a REST API.
- It also works with large scale deployments by
- integrating with OpenStack.</p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>LXD is the new LXC experience. It offers a
+ completely fresh and intuitive user experience
+ with a single command line tool to manage your
+ containers. Containers can be managed over the
+ network in a transparent way through a REST API.
+ It also works with large scale deployments by
+ integrating with OpenStack.</p>
- <p>
- <a class="p-button--positive" href="/lxd/try-it/" role="button">Try it</a>
- <a class="p-button" href="/lxd/introduction/" role="button">Learn more</a>
- </p>
- </div>
+ <p>
+ <a class="p-button--positive" href="/lxd/try-it/" role="button">Try it</a>
+ <a class="p-button" href="/lxd/introduction/" role="button">Learn more</a>
+ </p>
+ </div>
- <div class="p-card col-4">
- <h3>LXCFS</h3>
- <p>Userspace (FUSE) filesystem offering two main things:
- <ul>
- <li>Overlay files for cpuinfo, meminfo, stat and uptime.</li>
- <li>A cgroupfs compatible tree allowing unprivileged writes.</li>
- </ul>
- </p>
+ <div class="p-card col-4">
+ <h3>LXCFS</h3>
+ <p>Userspace (FUSE) filesystem offering two main things:
+ <ul>
+ <li>Overlay files for cpuinfo, meminfo, stat and uptime.</li>
+ <li>A cgroupfs compatible tree allowing unprivileged writes.</li>
+ </ul>
+ </p>
- <p>It's designed to workaround the shortcomings of procfs, sysfs
- and cgroupfs by exporting files which match what a system
- container user would expect.</p>
+ <p>It's designed to workaround the shortcomings of procfs, sysfs
+ and cgroupfs by exporting files which match what a system
+ container user would expect.</p>
- <p><a class="p-button" href="/lxcfs/introduction/" role="button">Learn more</a></p>
- </div>
+ <p><a class="p-button" href="/lxcfs/introduction/" role="button">Learn more</a></p>
</div>
+ </div>
</div>
<div class="p-strip">
- <div class="row">
- <div class="col-8">
- <h2>Deprecated projects</h2>
- </div>
- </div>
- <div class="row">
- <div class="col-6">
- <h3>CGManager</h3>
- <p>CGManager is our cgroup manager daemon. It's
- designed to allow nested unprivileged containers
- to still be able to create and manage their
- cgroups through a DBus API.</p>
+ <div class="row">
+ <div class="col-8">
+ <h2>Deprecated projects</h2>
+ <h3>CGManager</h3>
+ <p>CGManager is our cgroup manager daemon. It's
+ designed to allow nested unprivileged containers
+ to still be able to create and manage their
+ cgroups through a DBus API.</p>
- <p>CGManager was used by default with LXC in
- Ubuntu since April 2014 and then by other
- distributions as they started needing working
- unprivileged containers.</p>
+ <p>CGManager was used by default with LXC in
+ Ubuntu since April 2014 and then by other
+ distributions as they started needing working
+ unprivileged containers.</p>
- <p>It has now been deprecated in favor of the CGroup namespace
- in recent Linux kernels. On older kernels, LXCFS still offers
- a cgroupfs emulation that can be used instead of cgmanager
- and is more widely compatible with existing userspace.</p>
+ <p>It has now been deprecated in favor of the CGroup namespace
+ in recent Linux kernels. On older kernels, LXCFS still offers
+ a cgroupfs emulation that can be used instead of cgmanager
+ and is more widely compatible with existing userspace.</p>
- <p><a class="btn btn-primary" href="/cgmanager/introduction/" role="button">Learn more ›</a></p>
- </div>
+ <p><a class="p-button" href="/cgmanager/introduction/" role="button">Learn more ›</a></p>
</div>
+ </div>
</div>
diff --git a/content/index.ja.html b/content/index.ja.html
index fb6cbb0..ad87a6d 100644
--- a/content/index.ja.html
+++ b/content/index.ja.html
@@ -1,150 +1,162 @@
-<h2>LinuxContainers.org <span class="text-muted">Infrastructure for container projects.</span></h2>
-<div class="large_content">
- <p><img src="/static/img/containers.png"
- alt="logo"/>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>Infrastructure for container projects.</h1>
+ <p>
<!--
- linuxcontainers.org is the umbrella project behind LXC,
- LXD and LXCFS. -->
- linuxcontainers.org は LXC、LXD、LXCFS を傘下に持つプロジェクトです。</p>
- </p>
+ linuxcontainers.org is the umbrella project behind LXC,
+ LXD and LXCFS. -->
+ linuxcontainers.org は LXC、LXD、LXCFS を傘下に持つプロジェクトです
+ </p>
- <p>
- <!--
- The goal is to offer a distro and vendor neutral environment
- for the development of Linux container technologies.
- -->
- このプロジェクトの目的は、Linux のコンテナ技術を開発するための、ディストリビューションやベンダから中立の環境を提供することです。
- </p>
+ <p>
+ <!--
+ The goal is to offer a distro and vendor neutral environment
+ for the development of Linux container technologies.
+ -->
+ このプロジェクトの目的は、Linux のコンテナ技術を開発するための、ディストリビューションやベンダから中立の環境を提供することです。
+ </p>
- <p>
- <!--
- Our main focus is system containers. That is, containers which
- offer an environment as close as possible as the one you'd get from a
- VM but without the overhead that comes with running a separate
- kernel and simulating all the hardware.
- -->
- 私たちは主にシステムコンテナにフォーカスを当てています。つまり、VM の環境に可能な限り近い環境でありながら、VM のように環境ごとに別々のカーネルを実行したり、ハードウェアをシミュレートすることによるオーバーヘッドがない環境を提供するコンテナです。
- </p>
+ <p>
+ <!--
+ Our main focus is system containers. That is, containers which
+ offer an environment as close as possible as the one you'd get from a
+ VM but without the overhead that comes with running a separate
+ kernel and simulating all the hardware.
+ -->
+ 私たちは主にシステムコンテナにフォーカスを当てています。つまり、VM の環境に可能な限り近い環境でありながら、VM のように環境ごとに別々のカーネルを実行したり、ハードウェアをシミュレートすることによるオーバーヘッドがない環境を提供するコンテナです。
+ </p>
+ </div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
-<hr/>
-<h2>活動中のプロジェクト <!-- Active projects --></h2>
-<div class="row">
- <div class="col-md-4">
- <h3>LXC</h3>
- <p>
- <!--
- LXC is the well known set of tools, templates,
- library and language bindings. It's pretty low
- level, very flexible and covers just about every
- containment feature supported by the upstream
- kernel.
- -->
- LXC はツール、テンプレート、ライブラリ、言語バインディングの良く知られたセットです。低レイヤで非常に柔軟性に富んでおり、Upstream のカーネルがサポートするほとんどのコンテナ関連機能をカバーします。
- </p>
- <p>
- <!--
- LXC is production ready with LXC 1.0 getting 5
- years of security updates and bugfixes
- (until April 2019).
- -->
- LXC は production ready であり、LXC 1.0 が 5 年間のセキュリティアップデートとバグ修正を提供します (2019 年 4 月まで)。
- </p>
- <p><a class="btn btn-primary" href="/ja/lxc/introduction/" role="button">詳しく見る »</a></p>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>活動中のプロジェクト <!-- Active projects --></h2>
+ </div>
+ </div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>
+ <!--
+ LXC is the well known set of tools, templates,
+ library and language bindings. It's pretty low
+ level, very flexible and covers just about every
+ containment feature supported by the upstream
+ kernel.
+ -->
+ LXC はツール、テンプレート、ライブラリ、言語バインディングの良く知られたセットです。低レイヤで非常に柔軟性に富んでおり、Upstream のカーネルがサポートするほとんどのコンテナ関連機能をカバーします。
+ </p>
+ <p>
+ <!--
+ LXC is production ready with LXC 1.0 getting 5
+ years of security updates and bugfixes
+ (until April 2019).
+ -->
+ LXC は production ready であり、LXC 1.0 が 5 年間のセキュリティアップデートとバグ修正を提供します (2019 年 4 月まで)。
+ </p>
+ <p><a class="p-button" href="/ja/lxc/introduction/" role="button">詳しく見る</a></p>
</div>
- <div class="col-md-4">
- <h3>LXD</h3>
- <p>
- <!--
- LXD is the new LXC experience. It offers a
- completely fresh and intuitive user experience
- with a single command line tool to manage your
- containers. Containers can be managed over the
- network in a transparent way through a REST API.
- It also works with large scale deployments by
- integrating with OpenStack.
- -->
- LXD は LXC の新しい体験です。コンテナを管理するための一つのコマンドラインツールで、完全に新鮮で直感的なユーザ体験を提供します。コンテナを REST API を通した透過的な方法でネットワーク経由で管理できます。LXD は OpenStack との統合により大規模のデプロイも扱います。
- </p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>
+ <!--
+ LXD is the new LXC experience. It offers a
+ completely fresh and intuitive user experience
+ with a single command line tool to manage your
+ containers. Containers can be managed over the
+ network in a transparent way through a REST API.
+ It also works with large scale deployments by
+ integrating with OpenStack.
+ -->
+ LXD は LXC の新しい体験です。コンテナを管理するための一つのコマンドラインツールで、完全に新鮮で直感的なユーザ体験を提供します。コンテナを REST API を通した透過的な方法でネットワーク経由で管理できます。LXD は OpenStack との統合により大規模のデプロイも扱います。
+ </p>
- <p>
- <a class="btn btn-primary" href="/lxd/try-it/" role="button">試してみる »</a>
- <a class="btn btn-primary" href="/lxd/introduction/" role="button">詳しく見る »</a>
- </p>
+ <p>
+ <a class="p-button--positive" href="/lxd/try-it/" role="button">試してみる</a>
+ <a class="p-button" href="/lxd/introduction/" role="button">詳しく見る</a>
+ </p>
</div>
- <div class="col-md-6">
- <h3>LXCFS</h3>
- <p>
- <!--
+ <div class="p-card col-4">
+ <h3>LXCFS</h3>
+ <p>
+ <!--
Userspace (FUSE) filesystem offering two main things:
- -->
- 主に以下の2つを提供する FUSE を使ったユーザスペースのファイルシステムです:
- <ul>
- <li>
- <!--
- Overlay files for cpuinfo, meminfo, stat and uptime.
- -->
- cpuinfo, meminfo, stat, uptime のためのファイルを差し替えます
- </li>
- <li>
- <!--
- A cgroupfs compatible tree allowing unprivileged writes.
- -->
- 一般ユーザ権限でも書き込める cgroupfs 互換のツリーを提供します
- </li>
- </ul>
- </p>
+ -->
+ 主に以下の2つを提供する FUSE を使ったユーザスペースのファイルシステムです:
+ <ul>
+ <li>
+ <!--
+ Overlay files for cpuinfo, meminfo, stat and uptime.
+ -->
+ cpuinfo, meminfo, stat, uptime のためのファイルを差し替えます
+ </li>
+ <li>
+ <!--
+ A cgroupfs compatible tree allowing unprivileged writes.
+ -->
+ 一般ユーザ権限でも書き込める cgroupfs 互換のツリーを提供します
+ </li>
+ </ul>
+ </p>
- <p>
- <!--
- It's designed to workaround the shortcomings of procfs, sysfs
- and cgroupfs by exporting files which match what a system
- container user would expect.
- -->
- このファイルシステムは、システムコンテナのユーザが期待する情報を書き出すことによって、procfs、sysfs、cgroupfs の欠点を回避するようにデザインされます。
- </p>
+ <p>
+ <!--
+ It's designed to workaround the shortcomings of procfs, sysfs
+ and cgroupfs by exporting files which match what a system
+ container user would expect.
+ -->
+ このファイルシステムは、システムコンテナのユーザが期待する情報を書き出すことによって、procfs、sysfs、cgroupfs の欠点を回避するようにデザインされます。
+ </p>
- <p><a class="btn btn-primary" href="/ja/lxcfs/introduction/" role="button">詳しく見る »</a></p>
+ <p><a class="p-button" href="/ja/lxcfs/introduction/" role="button">詳しく見る</a></p>
</div>
+ </div>
</div>
-<hr/>
-<h2>廃止予定のプロジェクト <!-- Deprecated projects --></h2>
-<div class="row">
- <div class="col-md-6">
- <h3>CGManager</h3>
- <p>
- <!--
- CGManager is our cgroup manager daemon. It's
- designed to allow nested unprivileged containers
- to still be able to create and manage their
- cgroups through a DBus API.
- -->
- CGManager は cgroup を管理するデーモンです。DBus API を通して、ネストした非特権コンテナであっても、コンテナを作成してそのコンテナの cgroup を管理できるように設計されています。
- </p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ <h2>廃止予定のプロジェクト <!-- Deprecated projects --></h2>
+ <h3>CGManager</h3>
+ <p>
+ <!--
+ CGManager is our cgroup manager daemon. It's
+ designed to allow nested unprivileged containers
+ to still be able to create and manage their
+ cgroups through a DBus API.
+ -->
+ CGManager は cgroup を管理するデーモンです。DBus API を通して、ネストした非特権コンテナであっても、コンテナを作成してそのコンテナの cgroup を管理できるように設計されています。
+ </p>
- <p>
- <!--
- CGManager has been used by default with LXC in
- Ubuntu since April 2014 and then by other
- distributions as they start needing working
- unprivileged containers.
- -->
- CGManager は 2014 年 4 月から Ubuntu の LXC がデフォルトで使用しています。非特権コンテナの動作が必要な他のディストリビューションでも使用されています。
- </p>
+ <p>
+ <!--
+ CGManager has been used by default with LXC in
+ Ubuntu since April 2014 and then by other
+ distributions as they start needing working
+ unprivileged containers.
+ -->
+ CGManager は 2014 年 4 月から Ubuntu の LXC がデフォルトで使用しています。非特権コンテナの動作が必要な他のディストリビューションでも使用されています。
+ </p>
- <p>
- <!--
- It has now been deprecated in favor of the CGroup namespace
- in recent Linux kernels. On older kernels, LXCFS still offers
- a cgroupfs emulation that can be used instead of cgmanager
- and is more widely compatible with existing userspace.
- -->
- CGManager は最近のカーネルに cgroup namespace が実装されたため廃止予定です。古いカーネルに対しては LXCFS が cgroupfs のエミュレーション機能を提供します。LXCFS のほうが広い環境に対応できます。
- </p>
+ <p>
+ <!--
+ It has now been deprecated in favor of the CGroup namespace
+ in recent Linux kernels. On older kernels, LXCFS still offers
+ a cgroupfs emulation that can be used instead of cgmanager
+ and is more widely compatible with existing userspace.
+ -->
+ CGManager は最近のカーネルに cgroup namespace が実装されたため廃止予定です。古いカーネルに対しては LXCFS が cgroupfs のエミュレーション機能を提供します。LXCFS のほうが広い環境に対応できます。
+ </p>
- <p><a class="btn btn-primary" href="/ja/cgmanager/introduction/" role="button">詳しく見る »</a></p>
+ <p><a class="btn btn-primary" href="/ja/cgmanager/introduction/" role="button">詳しく見る</a></p>
</div>
+ </div>
</div>
diff --git a/content/index.ko.html b/content/index.ko.html
index 61ec26a..937141a 100644
--- a/content/index.ko.html
+++ b/content/index.ko.html
@@ -1,85 +1,96 @@
-<h2>LinuxContainers.org <span class="text-muted">컨테이너 프로젝트들을 위한 인프라스트럭처</span></h2>
-<div class="large_content">
- <p><img src="/static/img/containers.png"
- alt="logo"/>
- linuxcontainers.org는 LXC, LXD, LXCFS, CGManager를 모두 아우르는
- 프로젝트 입니다.</p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>컨테이너 프로젝트들을 위한 인프라스트럭처</h1>
+ <p>linuxcontainers.org는 LXC, LXD, LXCFS, CGManager를 모두 아우르는
+ 프로젝트 입니다.</p>
- <p>목표는 배포판과 벤더(vender) 중립적인 리눅스 컨테이너 기술 개발 환경을
- 제공하는 것입니다.</p>
+ <p>목표는 배포판과 벤더(vender) 중립적인 리눅스 컨테이너 기술 개발 환경을
+ 제공하는 것입니다.</p>
- <p>우리의 주안점은 시스템 컨테이너입니다. 즉, 독립적인 커널을 구동하거나
- 하드웨어를 시뮬레이션하는 오버헤드 없이 가상머신과 유사한 환경을
- 제공해 주는 것입니다.</p>
+ <p>우리의 주안점은 시스템 컨테이너입니다. 즉, 독립적인 커널을 구동하거나
+ 하드웨어를 시뮬레이션하는 오버헤드 없이 가상머신과 유사한 환경을
+ 제공해 주는 것입니다.</p>
- <p>이는 네임스페이스, 강제적 접근 제어(MAC), 컨트롤 그룹과 같은 여러
- 커널 보안 요소의 조합으로 이룰 수 있습니다.</p>
+ <p>이는 네임스페이스, 강제적 접근 제어(MAC), 컨트롤 그룹과 같은 여러
+ 커널 보안 요소의 조합으로 이룰 수 있습니다.</p>
+ </div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
-<hr/>
-<h2>진행 중인 프로젝트들</span></h2>
-<div class="row">
- <div class="col-md-4">
- <h3>LXC</h3>
- <p>LXC는 도구, 템플릿, 라이브러리, 프로그래밍 언어 바인딩으로 구성된
- 잘 알려진 세트입니다.
- 매우 저레벨이고 유연하며, 최신 커널이 지원하는 모든 컨테이너
- 기능 들을 다루고 있습니다.</p>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>진행 중인 프로젝트들</h2>
+ </div>
+ </div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>LXC는 도구, 템플릿, 라이브러리, 프로그래밍 언어 바인딩으로 구성된
+ 잘 알려진 세트입니다.
+ 매우 저레벨이고 유연하며, 최신 커널이 지원하는 모든 컨테이너
+ 기능 들을 다루고 있습니다.</p>
<p>production ready를 위해, LXC 1.0는 향후 5년동안 보안업데이트와 버그 수정이 이루어집니다 (2019년 4월까지).</p>
- <p><a class="btn btn-primary" href="/ko/lxc/introduction/" role="button">더 알아보기 »</a></p>
+ <p><a class="p-button" href="/ko/lxc/introduction/" role="button">더 알아보기 </a></p>
</div>
- <div class="col-md-4">
- <h3>LXD</h3>
- <p>LXD는 새로운 LXC 사용 환경입니다.
- 컨테이너 관리를 위해 단 하나의 명령어 도구를 사용하며,
- 이를 통해 완전히 새롭고 직관적인 사용자 경험을 제공합니다.
- 컨테이너는 네트워크 위에서 REST API를 통해 투명한 방법으로 관리될 수
- 있습니다. 오픈스택과 함께 통합되어, 매우 큰 규모의 배포시스템에서도
- 동작 가능합니다.</p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>LXD는 새로운 LXC 사용 환경입니다.
+ 컨테이너 관리를 위해 단 하나의 명령어 도구를 사용하며,
+ 이를 통해 완전히 새롭고 직관적인 사용자 경험을 제공합니다.
+ 컨테이너는 네트워크 위에서 REST API를 통해 투명한 방법으로 관리될 수
+ 있습니다. 오픈스택과 함께 통합되어, 매우 큰 규모의 배포시스템에서도
+ 동작 가능합니다.</p>
- <p>LXD는 2014년 11월 초에 발표되었습니다. 그리고 현재까지도 활발하게 개발이 이루어지고 있습니다.</p>
+ <p>LXD는 2014년 11월 초에 발표되었습니다. 그리고 현재까지도 활발하게 개발이 이루어지고 있습니다.</p>
- <p>
- <a class="btn btn-primary" href="/ko/lxd/introduction/" role="button">더 알아보기 »</a>
- <a class="btn btn-primary" href="/ko/lxd/try-it/" role="button">체험해 보기 »</a>
- </p>
+ <p>
+ <a class="p-button" href="/ko/lxd/introduction/" role="button">더 알아보기 </a>
+ <a class="p-button" href="/ko/lxd/try-it/" role="button">체험해 보기 </a>
+ </p>
</div>
- <div class="col-md-6">
- <h3>LXCFS</h3>
- <p>아래 두가지를 제공하는 사용자영역 파일시스템 (FUSE) 입니다.
- <ul>
- <li>cpuinfo, meminfo, stat, uptime를 위한 오버레이 파일시스템.</li>
- <li>비특권 상태에서도 쓰기가 가능한 cgroupfs 호환 트리</li>
- </ul>
- </p>
+ <div class="p-card col-4">
+ <h3>LXCFS</h3>
+ <p>아래 두가지를 제공하는 사용자영역 파일시스템 (FUSE) 입니다.
+ <ul>
+ <li>cpuinfo, meminfo, stat, uptime를 위한 오버레이 파일시스템.</li>
+ <li>비특권 상태에서도 쓰기가 가능한 cgroupfs 호환 트리</li>
+ </ul>
+ </p>
- <p>시스템 컨테이너 사용자가 기대하는 정보들을 내보내서,
- procfs, sysfs, cgroupfs의 단점을 보완하도록 만들어졌습니다.</p>
+ <p>시스템 컨테이너 사용자가 기대하는 정보들을 내보내서,
+ procfs, sysfs, cgroupfs의 단점을 보완하도록 만들어졌습니다.</p>
- <p><a class="btn btn-primary" href="/ko/lxcfs/introduction/" role="button">더 알아보기 »</a></p>
+ <p><a class="p-button" href="/ko/lxcfs/introduction/" role="button">더 알아보기 </a></p>
</div>
+ </div>
</div>
-<hr/>
-<h2>종료된 프로젝트들</span></h2>
-<div class="row">
- <div class="col-md-6">
- <h3>CGManager</h3>
- <p>CGManager는 우리의 컨트롤 그룹 관리자 데몬입니다.
- 중첩된(nested) 비특권 컨테이너에게도 DBus API를 통해, 각자의
- 컨트롤 그룹을 생성/관리할 수 있게 해줍니다.</p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ <h2>종료된 프로젝트들</span></h2>
+ <h3>CGManager</h3>
+ <p>CGManager는 우리의 컨트롤 그룹 관리자 데몬입니다.
+ 중첩된(nested) 비특권 컨테이너에게도 DBus API를 통해, 각자의
+ 컨트롤 그룹을 생성/관리할 수 있게 해줍니다.</p>
- <p>CGManager는 2014년 4월부터 우분투에서 LXC가 기본으로 사용하고
- 있습니다. 그리고 비특권 컨테이너가 동작해야 하는 다른 배포판들에서도
- 사용되고 있습니다.</p>
+ <p>CGManager는 2014년 4월부터 우분투에서 LXC가 기본으로 사용하고
+ 있습니다. 그리고 비특권 컨테이너가 동작해야 하는 다른 배포판들에서도
+ 사용되고 있습니다.</p>
- <p>최근 리눅스 커널에 들어간 CGroup 네임스페이스로 대체되어
- 본 프로젝트는 더이상 사용되지 않습니다.
- 오래된 커널에서도 CGManager를 대신하여 LXCFS가 cgrou pfs 에뮬레이션을
- 제공해주고 있습니다. 그리고 LXCFS가 더 폭넓게 호환됩니다.</p>
+ <p>최근 리눅스 커널에 들어간 CGroup 네임스페이스로 대체되어
+ 본 프로젝트는 더이상 사용되지 않습니다.
+ 오래된 커널에서도 CGManager를 대신하여 LXCFS가 cgrou pfs 에뮬레이션을
+ 제공해주고 있습니다. 그리고 LXCFS가 더 폭넓게 호환됩니다.</p>
- <p><a class="btn btn-primary" href="/ko/cgmanager/introduction/" role="button">더 알아보기 »</a></p>
+ <p><a class="p-button" href="/ko/cgmanager/introduction/" role="button">더 알아보기 </a></p>
</div>
+ </div>
</div>
diff --git a/content/index.ru.html b/content/index.ru.html
index bdf09be..6282a4e 100644
--- a/content/index.ru.html
+++ b/content/index.ru.html
@@ -1,125 +1,138 @@
-<h2>
- LinuxContainers.org <span class="text-muted">Инфраструктура для контейнерных проектов.</span>
-</h2>
-<div class="large_content">
- <p>
- <img src="/static/img/containers.png" alt="logo"/>
- linuxcontainers.org является всеобъемлющим проектом стоящий за LXC,
- LXD, LXCFS и CGManager.
- </p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8 suffix-1">
+ <h1>Инфраструктура для контейнерных проектов.</h1>
+ <p>
+ linuxcontainers.org является всеобъемлющим проектом стоящий за LXC,
+ LXD, LXCFS и CGManager.
+ </p>
- <p>
- Цель проекта состоит в предоставлении дистрибутива и поставки нейтральной среды
- для развития контейнерных технологий Linux.
- </p>
+ <p>
+ Цель проекта состоит в предоставлении дистрибутива и поставки нейтральной среды
+ для развития контейнерных технологий Linux.
+ </p>
- <p>
- Наш основной упор делается на систему контейнеров.
- То есть, контейнеры, которые предоставляют условия,
- наиболее близкие к Виртуальной машине, но без накладных расходов,
- происходящих с запуском отдельного ядра и моделирования всего оборудования.
- </p>
+ <p>
+ Наш основной упор делается на систему контейнеров.
+ То есть, контейнеры, которые предоставляют условия,
+ наиболее близкие к Виртуальной машине, но без накладных расходов,
+ происходящих с запуском отдельного ядра и моделирования всего оборудования.
+ </p>
- <p>
- Это достигается за счет сочетания функций безопасности ядра,
- таких как: пространство имен, обязательного контроля доступа и контрольных групп
- </p>
+ <p>
+ Это достигается за счет сочетания функций безопасности ядра,
+ таких как: пространство имен, обязательного контроля доступа и контрольных групп
+ </p>
+ </div>
+ <div class="col-4">
+ <img src="/static/img/containers.png" alt="" />
+ </div>
+ </div>
</div>
-<hr/>
-<h2>
- Проекты. <span class="text-muted">Интересные факты.</span>
-</h2>
-<div class="row">
- <div class="col-md-4">
- <h3>LXC</h3>
- <p>
- LXC является известным набором инструментов, шаблонов,
- библиотек и языковых привязок.
- Это довольно низкий уровень,
- очень гибкий и охватывающий почти каждую особенность сдерживания,
- поддерживаемой в разработкe ядра.
- </p>
- <p>
- LXC является готовым для продакшена с LXC 1.0 c 5 летней поддержкой
- обновлений безопасности и исправлений (до апреля 2019 года).
- </p>
- <p>
- <a class="btn btn-primary" href="/lxc/introduction/" role="button">
- Подробнее »
- </a>
- </p>
+<div class="p-strip--light">
+ <div class="row">
+ <div class="col-8">
+ <h2>
+ Проекты. Интересные факты.
+ </h2>
+ </div>
</div>
+ <div class="row u-equal-height">
+ <div class="p-card col-4">
+ <h3>LXC</h3>
+ <p>
+ LXC является известным набором инструментов, шаблонов,
+ библиотек и языковых привязок.
+ Это довольно низкий уровень,
+ очень гибкий и охватывающий почти каждую особенность сдерживания,
+ поддерживаемой в разработкe ядра.
+ </p>
+ <p>
+ LXC является готовым для продакшена с LXC 1.0 c 5 летней поддержкой
+ обновлений безопасности и исправлений (до апреля 2019 года).
+ </p>
+ <p>
+ <a class="p-button" href="/lxc/introduction/" role="button">
+ Подробнее
+ </a>
+ </p>
+ </div>
- <div class="col-md-4">
- <h3>LXD</h3>
- <p>
- LXD это новый опыт LXC.
- Предлагающий полностью свежую и интуитивно
- понятную работу с помощью всего одного
- инструмента: командной строки для управления своими контейнерами.
- Контейнерами можно управлять прозрачным образом по сети
- через API REST.
- Технология так же работает с развертыванием масштабных сред
- путем интеграции с OpenStack.
- </p>
+ <div class="p-card col-4">
+ <h3>LXD</h3>
+ <p>
+ LXD это новый опыт LXC.
+ Предлагающий полностью свежую и интуитивно
+ понятную работу с помощью всего одного
+ инструмента: командной строки для управления своими контейнерами.
+ Контейнерами можно управлять прозрачным образом по сети
+ через API REST.
+ Технология так же работает с развертыванием масштабных сред
+ путем интеграции с OpenStack.
+ </p>
- <p>
- О LXD было объявлено в начале ноября 2014 года
- и по сей день он находится в очень активном развитии.
- </p>
+ <p>
+ О LXD было объявлено в начале ноября 2014 года
+ и по сей день он находится в очень активном развитии.
+ </p>
- <p>
- <a class="btn btn-primary" href="/lxd/introduction/" role="button">
- Подробнее »
- </a>
- </p>
- </div>
+ <p>
+ <a class="p-button" href="/lxd/introduction/" role="button">
+ Подробнее
+ </a>
+ </p>
+ </div>
- <div class="col-md-4">
- <h3>CGManager</h3>
- <p>
- CGManager - наш демон для упраления контролем групп.
- Он предназначен для работы с вложенными непривилегированными контейнерами
- позволяющий создавать и управлять
- своими контрольными группы через API DBus.
- </p>
+ <div class="p-card col-4">
+ <h3>CGManager</h3>
+ <p>
+ CGManager - наш демон для упраления контролем групп.
+ Он предназначен для работы с вложенными непривилегированными контейнерами
+ позволяющий создавать и управлять
+ своими контрольными группы через API DBus.
+ </p>
- <p>
- CGManager был использован по умолчанию с LXC в Ubuntu
- с апреля 2014 года, а затем в других дистрибутивах,
- как только в них появлялась необходимость
- в работе c непривилегированными контейнерами.
- </p>
+ <p>
+ CGManager был использован по умолчанию с LXC в Ubuntu
+ с апреля 2014 года, а затем в других дистрибутивах,
+ как только в них появлялась необходимость
+ в работе c непривилегированными контейнерами.
+ </p>
- <p>
- <a class="btn btn-primary" href="/cgmanager/introduction/" role="button">
- Подробнее »
- </a>
- </p>
+ <p>
+ <a class="p-button" href="/cgmanager/introduction/" role="button">
+ Подробнее
+ </a>
+ </p>
+ </div>
</div>
+</div>
- <div class="col-md-6">
- <h3>LXCFS</h3>
- <p>
- Пользовательское пространство (FUSE) файловая система предлагает двe основныe вещи:
- <ul>
- <li>Слой файлов для CPUInfo, MemInfo, stat и uptime.</li>
- <li>Cgroupfs совместимое дерево предоставлящее возможность непривилегированной записи.</li>
- </ul>
- </p>
+<div class="p-strip">
+ <div class="row">
+ <div class="col-8">
+ <h3>LXCFS</h3>
+ <p>
+ Пользовательское пространство (FUSE) файловая система предлагает двe основныe вещи:
+ <ul>
+ <li>Слой файлов для CPUInfo, MemInfo, stat и uptime.</li>
+ <li>Cgroupfs совместимое дерево предоставлящее возможность непривилегированной записи.</li>
+ </ul>
+ </p>
- <p>
- Предназначена для обхода недостатков PROCFS,
- sysfs и cgroupfs при экспорте файлов,
- соответствующие тeм,
- которые пользователь системы контейнера ожидает.
- </p>
+ <p>
+ Предназначена для обхода недостатков PROCFS,
+ sysfs и cgroupfs при экспорте файлов,
+ соответствующие тeм,
+ которые пользователь системы контейнера ожидает.
+ </p>
- <p>
- <a class="btn btn-primary" href="/lxcfs/introduction/" role="button">
- Подробнее »
- </a>
- </p>
+ <p>
+ <a class="p-button" href="/lxcfs/introduction/" role="button">
+ Подробнее
+ </a>
+ </p>
+ </div>
</div>
</div>
diff --git a/templates/common/footer.fr.tpl.html b/templates/common/footer.fr.tpl.html
index 91aea12..5afc879 100644
--- a/templates/common/footer.fr.tpl.html
+++ b/templates/common/footer.fr.tpl.html
@@ -1,9 +1,18 @@
-<hr class="footer"/>
-<footer>
- <p class="pull-left"><a href="https://github.com/lxc/linuxcontainers.org">Améliorez ce site web</a></p>
- <p class="pull-right"><a href="#">Remonter</a></p>
- <p class="text-center">
- <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Contenu sous licence Creative Commons CC BY NC SA</a><br />
- <span class="small">Projet supporté par <a href="http://www.canonical.com">Canonical Ltd.</a></span>
- </p>
+<footer class="p-footer">
+ <div class="row">
+ <p>Projet supporté par <a href="http://www.canonical.com">Canonical Ltd.</p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">Améliorez ce site web</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">Remonter</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Contenu sous licence Creative Commons CC BY NC SA</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
diff --git a/templates/common/footer.ja.tpl.html b/templates/common/footer.ja.tpl.html
index c157331..03f8d73 100644
--- a/templates/common/footer.ja.tpl.html
+++ b/templates/common/footer.ja.tpl.html
@@ -1,9 +1,18 @@
-<hr class="footer"/>
-<footer>
- <p class="pull-left"><a href="https://github.com/lxc/linuxcontainers.org">このサイトをより良くする</a></p>
- <p class="pull-right"><a href="#">ページの上部へ戻る</a></p>
- <p class="text-center">
- <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">コンテンツはクリエイティブ・コモンズ CC BY NC SA の下に提供されています</a><br />
- <span class="small">このプロジェクトは <a href="http://www.canonical.com">Canonical Ltd.</a> の支援を受けています。</span>
- </p>
+<footer class="p-footer">
+ <div class="row">
+ <p>このプロジェクトは <a href="http://www.canonical.com">Canonical Ltd.</a> の支援を受けています。</p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">このサイトをより良くする</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">ページの上部へ戻る</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">コンテンツはクリエイティブ・コモンズ CC BY NC SA の下に提供されています</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
diff --git a/templates/common/footer.ko.tpl.html b/templates/common/footer.ko.tpl.html
index decb92d..070ea76 100644
--- a/templates/common/footer.ko.tpl.html
+++ b/templates/common/footer.ko.tpl.html
@@ -1,9 +1,18 @@
-<hr class="footer"/>
-<footer>
- <p class="pull-left"><a href="https://github.com/lxc/linuxcontainers.org">이 사이트를 개선하고 싶다면</a></p>
- <p class="pull-right"><a href="#">맨 위로</a></p>
- <p class="text-center">
- <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">이 내용은 크리에이티브 커먼즈 CC BY NC SA 로 제공 되고 있습니다.</a><br />
- <span class="small">이 프로젝트는 <a href="http://www.canonical.com">Canonical Ltd.</a>의 지원을 받고 있습니다.</span>
- </p>
+<footer class="p-footer">
+ <div class="row">
+ <p>이 프로젝트는 <a href="http://www.canonical.com">Canonical Ltd.</a>의 지원을 받고 있습니다.</p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">이 사이트를 개선하고 싶다면</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">맨 위로</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">이 내용은 크리에이티브 커먼즈 CC BY NC SA 로 제공 되고 있습니다.</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
diff --git a/templates/common/footer.ru.tpl.html b/templates/common/footer.ru.tpl.html
index bb500a8..f8d2c7b 100644
--- a/templates/common/footer.ru.tpl.html
+++ b/templates/common/footer.ru.tpl.html
@@ -1,9 +1,19 @@
-<hr class="footer"/>
-<footer>
- <p class="pull-left"><a href="https://github.com/lxc/linuxcontainers.org">Улучшить этот вебсайт</a></p>
- <p class="pull-right"><a href="#">Наверх</a></p>
- <p class="text-center">
- <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Содержимое распространяется по лицензии Creative Commons CC BY NC SA</a><br />
- <span class="small">Проект спонсируется <a href="http://www.canonical.com">Canonical Ltd.</a></span>
- </p>
+<footer class="p-footer">
+ <div class="row">
+ <p>Проект спонсируется <a href="http://www.canonical.com">Canonical Ltd.</a></p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">Улучшить этот вебсайт</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">Наверх</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Содержимое распространяется по лицензии Creative Commons CC BY NC SA</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
+
diff --git a/templates/common/footer.tpl.html b/templates/common/footer.tpl.html
index 302d0b5..81f13bf 100644
--- a/templates/common/footer.tpl.html
+++ b/templates/common/footer.tpl.html
@@ -1,18 +1,18 @@
<footer class="p-footer">
- <div class="row">
- <p>Project sponsored by <a href="http://www.canonical.com">Canonical Ltd.</a></p>
- <nav class="p-footer__nav">
- <ul class="p-inline-list--middot u-no-margin--bottom">
- <li class="p-inline-list__item">
- <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">Improve this website</a>
- </li>
- <li class="p-inline-list__item">
- <a class="p-link--soft" href="#">Back to top</a>
- </li>
- <li class="p-inline-list__item">
- <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Content under Creative Commons CC BY NC SA</a>
- </li>
- </ul>
- </nav>
- </div>
+ <div class="row">
+ <p>Project sponsored by <a href="http://www.canonical.com">Canonical Ltd.</a></p>
+ <nav class="p-footer__nav">
+ <ul class="p-inline-list--middot u-no-margin--bottom">
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://github.com/lxc/linuxcontainers.org">Improve this website</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="#">Back to top</a>
+ </li>
+ <li class="p-inline-list__item">
+ <a class="p-link--soft" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Content under Creative Commons CC BY NC SA</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
</footer>
From 40330f707f91ef2d56d275ba6a75312bfc5cbf67 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Wed, 1 Nov 2017 10:41:21 +0000
Subject: [PATCH 6/8] Updated try it to Vanilla
---
content/lxd/try-it.html | 2 +-
content/lxd/try-it.ja.html | 808 +++++++++++++++++++--------------------------
2 files changed, 339 insertions(+), 471 deletions(-)
diff --git a/content/lxd/try-it.html b/content/lxd/try-it.html
index b0985b3..df25c50 100644
--- a/content/lxd/try-it.html
+++ b/content/lxd/try-it.html
@@ -3,7 +3,7 @@
<script src="/static/js/term.js" type="text/javascript"></script>
<script src="/static/js/bootstrap-rating.min.js" type="text/javascript"></script>
<script src="/static/js/tryit.js" type="text/javascript"></script>
-<div class="p-strip">
+<div class="p-strip--shallow">
<div class="row">
<div class="col-12">
<noscript>
diff --git a/content/lxd/try-it.ja.html b/content/lxd/try-it.ja.html
index e0b47f5..32d2ea8 100644
--- a/content/lxd/try-it.ja.html
+++ b/content/lxd/try-it.ja.html
@@ -2,617 +2,485 @@
<script src="/static/js/getEmPixels.js" type="text/javascript"></script>
<script src="/static/js/term.js" type="text/javascript"></script>
<script src="/static/js/tryit.js" type="text/javascript"></script>
+<div class="p-strip--shallow">
+ <div class="row">
+ <div class="col-12">
+ <div class="p-notification--negative" id="tryit_status_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">>サーバの状態 <!-- Server status --></span>
+ <span class="p-notification__body" id="tryit_online_message" style="display:none">
+ 接続元 <!-- You are connected over: --><span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
+ デモサーバは現在ユーザセッションを <span id="tryit_count"></span> セッション実行中です (最大 <span id="tryit_max"></span> セッション中)<!-- The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span> -->
+ </span>
+
+ <span class="p-notification__body" id="tryit_maintenance_message" style="display:none">
+ <!--
+ The demo service is currently down for maintenance and should be
+ back online in a few minutes.
+ -->
+ デモサービスは現在メンテナンスのために停止しています。数分後にはサービスを再開する予定です。
+ </span>
+
+ <span class="p-notification__body" id="tryit_unreachable_message" style="display:none">
+ <!--
+ Your browser couldn't reach the demo server.<br />
+ This is either (most likely) because of a firewall or proxy
+ issue on your side or because of a network, power or other catastrophic
+ server side failure.
+ -->
+ あなたがお使いのブラウザからデモサーバへアクセスできません。<br />
+ おそらく、あなたのサイトのファイアウォールかプロキシの問題、もしくはサーバ側のネットワーク、電源、その他の深刻な障害のためと思われます。
+ </span>
+ </p>
+ </div>
-<div class="panel panel-success" id="tryit_status_panel" style="display:none">
- <div class="panel-heading">サーバの状態 <!-- Server status --></div>
- <div class="panel-body" id="tryit_online_message" style="display:none">
- 接続元 <!-- You are connected over: --><span id="tryit_protocol"></span> (<span id="tryit_address"></span>)<br/>
- デモサーバは現在ユーザセッションを <span id="tryit_count"></span> セッション実行中です (最大 <span id="tryit_max"></span> セッション中)<!-- The demo server is currently running <span id="tryit_count"></span> user sessions out of <span id="tryit_max"></span> -->
- </div>
-
- <div class="panel-body" id="tryit_maintenance_message" style="display:none">
- <!--
- The demo service is currently down for maintenance and should be
- back online in a few minutes.
- -->
- デモサービスは現在メンテナンスのために停止しています。数分後にはサービスを再開する予定です。
- </div>
-
- <div class="panel-body" id="tryit_unreachable_message" style="display:none">
- <!--
- Your browser couldn't reach the demo server.<br />
- This is either (most likely) because of a firewall or proxy
- issue on your side or because of a network, power or other catastrophic
- server side failure.
- -->
- あなたがお使いのブラウザからデモサーバへアクセスできません。<br />
- おそらく、あなたのサイトのファイアウォールかプロキシの問題、もしくはサーバ側のネットワーク、電源、その他の深刻な障害のためと思われます。
- </div>
-</div>
-
-<div class="panel panel-primary" id="tryit_terms_panel" style="display:none">
- <div class="panel-heading">サービス利用規約 <!-- Terms of service --></div>
- <div class="panel-body" id="tryit_terms"></div>
-</div>
-
-<div class="panel panel-warning" id="tryit_start_panel" style="display:none">
- <div class="panel-heading">試用開始 <!-- Start --></div>
- <div class="panel-body">
- <button class="btn btn-default btn-lg" id="tryit_accept" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-ok"></span>
- 私はサービス利用規約を読み、同意しました<!-- I have read and accept the terms of service above -->
- </button>
-
- <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
- <p>
- <big>コンテナの起動中... <!-- Starting the container... --></big>
- </p>
- <p>
- <div class="large spinner"></div>
- </p>
- </div>
+ <div class="p-notification--information" id="tryit_terms_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">サービス利用規約 <!-- Terms of service --></span>
+ <div class="p-notification__body" id="tryit_terms"></div>
+ </p>
+ </div>
- </div>
-</div>
+ <div class="p-notification--caution" id="tryit_start_panel" style="display:none">
+ <p class="p-notification__response">
+ <span class="p-notification__status">試用開始 <!-- Start --></span>
+ <div class="p-notification__body">
+ <button class="p-button" id="tryit_accept" type="button">
+ <i aria-hidden="true" class="p-icon--success"></i>
+ 私はサービス利用規約を読み、同意しました<!-- I have read and accept the terms of service above -->
+ </button>
+
+ <div id="tryit_progress" style="display:none;width:100%;text-align:center;">
+ <p class="p-heading--four">コンテナの起動中... <!-- Starting the container... --></p>
+ <p>
+ <i class="p-icon--spinner u-animation--spin"></i>
+ </p>
+ </div>
+ </div>
+ </p>
+ </div>
-<div class="panel panel-success" id="tryit_info_panel" style="display:none">
- <div class="panel-heading">コンテナの情報 <!-- Container information --></div>
- <table class="table" style="padding-left: 15px;">
- <tr id="tryit_lxd_row">
- <th>LXD</th>
- <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
- </tr>
-
- <tr id="tryit_clock">
- <th>残り時間 <!-- Time --></th>
- <td><span class="minutes"></span> 分<!-- minutes, --> <span class="seconds"></span> 秒<!-- seconds --></td>
- </tr>
- </table>
-</div>
+ <div class="p-notification--positive" id="tryit_info_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status">コンテナの情報 <!-- Container information --></span>
+ <div class="p-notification__body">
+ <table class="table">
+ <tr id="tryit_lxd_row">
+ <th>LXD</th>
+ <td>lxc remote add tryit <span class="tryit_container_ip"></span> --password=<span class="tryit_container_password"></span></td>
+ </tr>
+
+ <tr id="tryit_clock">
+ <th>残り時間 <!-- Time --></th>
+ <td><span class="minutes"></span> 分<!-- minutes, --> <span class="seconds"></span> 秒<!-- seconds --></td>
+ </tr>
+ </table>
+ </div>
+ </div>
+ </div>
-<div class="panel panel-primary" id="tryit_console_panel" style="display:none">
- <div class="panel-heading">コンソール <!-- Console --></div>
- <div id="tryit_console" style="background-color:black;"></div>
+ <div class="p-notification" id="tryit_console_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status">コンソール <!-- Console --></span>
+ <div id="tryit_console" style="background-color:black;"></div>
- <button class="btn btn-default btn-lg" id="tryit_console_reconnect" type="button" style="display:none">
- <span aria-hidden="true" class="glyphicon glyphicon-repeat"></span>
- 再接続 <!-- Reconnect -->
- </button>
-</div>
-
-<div class="panel panel-warning" id="tryit_examples_panel" style="display:none">
- <div class="panel-heading"><a data-toggle="collapse" class="text" href="#tryit_examples_collapse">ステップバイステップでの入門</a> <!-- Step by step introduction --></div>
- <div class="panel-body collapse in" id="tryit_examples_collapse">
- <div class="panel-group" role="tablist" id="tryit_intro"
- aria-multiselectable="true">
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h1">
- <h4 class="panel-title">
- <a role="button" data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b1"
- aria-expanded="true" aria-controls="tryit_intro_b1">
- 1. はじめに <!-- Introduction -->
- </a>
- </h4>
+ <button class="p-button" id="tryit_console_reconnect" type="button" style="display:none">
+ 再接続 <!-- Reconnect -->
+ </button>
</div>
- <div class="panel-collapse collapse in" id="tryit_intro_b1"
- role="tabpanel" aria-labelledby="tryit_intro_h1">
- <div class="panel-body">
+ </div>
+
+ <div class="p-notification--caution" id="tryit_examples_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status"><a href="#introduction">ステップバイステップでの入門</a></span> <!-- Step by step introduction -->
+ <div class="tab-content" id="introduction">
+ <h3>1. はじめに <!-- Introduction --></h3>
<p><!-- You are now root inside a LXD container with a
- nested LXD installed inside it. -->
- 今、あなたは LXD コンテナ内に root としてログインしています。このコンテナには LXD がネストしてインストールされています。
+ nested LXD installed inside it. -->
+ 今、あなたは LXD コンテナ内に root としてログインしています。このコンテナには LXD がネストしてインストールされています。
</p>
<p><!-- Initial startup can take a few seconds due to
- having to generate SSL keys on a rather busy system.
- <br />
- Further commands should then be near instantaneous. -->
- 多少負荷のある状態で SSL 鍵を生成する必要があるため、最初の起動には数秒かかる可能性があります。<br/>
- それ以降に実行するコマンドはすぐに実行されるはずです。
+ having to generate SSL keys on a rather busy system.
+ <br />
+ Further commands should then be near instantaneous. -->
+ 多少負荷のある状態で SSL 鍵を生成する必要があるため、最初の起動には数秒かかる可能性があります。<br/>
+ それ以降に実行するコマンドはすぐに実行されるはずです。
</p>
<p><!-- You're welcome to just poke around and
- discover LXD through its manpage and \-\-help
- option.
- <br />
- Or you can follow this step by step tutorial
- instead which will get you through LXD's
- main features. -->
- 自由に色々やってみて、man ページや --help オプションを使って LXD について発見してみてください。
- <br />
- もしくは、このステップバイステップのチュートリアルを使って、LXDの主な機能を学んでも良いでしょう。
-
+ discover LXD through its manpage and \-\-help
+ option.
+ <br />
+ Or you can follow this step by step tutorial
+ instead which will get you through LXD's
+ main features. -->
+ 自由に色々やってみて、man ページや --help オプションを使って LXD について発見してみてください。
+ <br />
+ もしくは、このステップバイステップのチュートリアルを使って、LXDの主な機能を学んでも良いでしょう。
</p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h2">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b2"
- aria-expanded="false"
- aria-controls="tryit_intro_b2">
- 2. 最初のコンテナ <!-- Your first container -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b2"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="first-container">
+ <h3>2. 最初のコンテナ <!-- Your first container --></h3>
<p><!-- LXD is image based, however by default no
- images are loaded into the image store as can
- be seen with: -->
- LXD はイメージベースです。しかし、デフォルトでは以下のコマンドの結果のように、イメージはロードされていません: <pre>lxc image list</pre>
- </p>
-
- <p><!-- LXD knows about 3 default image servers: -->
- LXD はデフォルトでイメージサーバが 3 つ登録されています:
- <ul>
- <li>ubuntu: (Ubuntu stable イメージ用 <!-- for Ubuntu stable images -->)</li>
- <li>ubuntu-daily: (Ubuntu daily イメージ用 <!-- for Ubuntu daily images -->)</li>
- <li>images: (その他多数のディストリビューション用 <!-- for a bunch of other distributions -->)</li>
- </ul>
- </p>
-
- <p><!-- The stable Ubuntu images can be listed with: -->
- stable の Ubuntu イメージは以下のようにリスト表示できます:
- <pre>lxc image list ubuntu: | less</pre>
- </p>
-
- <p><!-- To launch a first container called "first"
- using the Ubuntu 16.04 image, use: -->
- "first" という名前の最初のコンテナを起動するには、以下のようにします:
- <pre>lxc launch ubuntu:16.04 first</pre>
- </p>
-
- <p><!-- Your new container will now be visible in: -->
- あなたが作成した新しいコンテナは以下のようにして確認できます。
- <pre>lxc list</pre>
- </p>
-
- <p><!-- Running state details and configuration can
- be queried with: -->
- コンテナの状態と設定は以下のようにして確認できます。
- <pre>lxc info first
-lxc config show first</pre>
- </p>
+ images are loaded into the image store as can
+ be seen with: -->
+ LXD はイメージベースです。しかし、デフォルトでは以下のコマンドの結果のように、イメージはロードされていません: <pre>lxc image list</pre>
+ </p>
+
+ <p><!-- LXD knows about 3 default image servers: -->
+ LXD はデフォルトでイメージサーバが 3 つ登録されています:
+ <ul>
+ <li>ubuntu: (Ubuntu stable イメージ用 <!-- for Ubuntu stable images -->)</li>
+ <li>ubuntu-daily: (Ubuntu daily イメージ用 <!-- for Ubuntu daily images -->)</li>
+ <li>images: (その他多数のディストリビューション用 <!-- for a bunch of other distributions -->)</li>
+ </ul>
+ </p>
+
+ <p><!-- The stable Ubuntu images can be listed with: -->
+ stable の Ubuntu イメージは以下のようにリスト表示できます:
+ <pre>lxc image list ubuntu: | less</pre>
+ </p>
+
+ <p><!-- To launch a first container called "first"
+ using the Ubuntu 16.04 image, use: -->
+ "first" という名前の最初のコンテナを起動するには、以下のようにします:
+ <pre>lxc launch ubuntu:16.04 first</pre>
+ </p>
+
+ <p><!-- Your new container will now be visible in: -->
+ あなたが作成した新しいコンテナは以下のようにして確認できます。
+ <pre>lxc list</pre>
+ </p>
+
+ <p><!-- Running state details and configuration can
+ be queried with: -->
+ コンテナの状態と設定は以下のようにして確認できます。
+ <pre>lxc info first
+ lxc config show first</pre>
+ </p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h3">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b3"
- aria-expanded="false"
- aria-controls="tryit_intro_b3">
- 3. リソース制限<!-- Limiting resources -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b3"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="limiting-resources">
+ <h3>3. リソース制限<!-- Limiting resources --></h3>
<p><!-- By default your container comes with no
- resource limitation and inherits from its
- parent environment. You can confirm it with: -->
- デフォルトでは、あなたの作成したコンテナはリソース制限がなく、自身の親環境のリソースをそのまま引き継いでいます。これは以下のように確認できます。
- <pre>free -m
-lxc exec first -- free -m</pre>
- </p>
-
- <p><!-- To apply a memory limit to your container, do: -->
- あなたが作成したコンテナに制限を追加するには以下のよう実行します。
- <pre>lxc config set first limits.memory 128MB</pre>
- </p>
-
- <p><!-- And confirm that it's been applied with: -->
- そして、制限が適用されたことを確認するには以下のように実行します。
- <pre>lxc exec first -- free -m</pre>
- </p>
+ resource limitation and inherits from its
+ parent environment. You can confirm it with: -->
+ デフォルトでは、あなたの作成したコンテナはリソース制限がなく、自身の親環境のリソースをそのまま引き継いでいます。これは以下のように確認できます。
+ <pre>free -m
+ lxc exec first -- free -m</pre>
+ </p>
+
+ <p><!-- To apply a memory limit to your container, do: -->
+ あなたが作成したコンテナに制限を追加するには以下のよう実行します。
+ <pre>lxc config set first limits.memory 128MB</pre>
+ </p>
+
+ <p><!-- And confirm that it's been applied with: -->
+ そして、制限が適用されたことを確認するには以下のように実行します。
+ <pre>lxc exec first -- free -m</pre>
+ </p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h4">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b4"
- aria-expanded="false"
- aria-controls="tryit_intro_b4">
- 4. スナップショット <!-- Snapshots -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b4"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="snapshots">
+ <h3>4. スナップショット <!-- Snapshots --></h3>
<p><!-- LXD supports snapshoting and restoring
- container snapshots.
- <br />
- Before making a snapshot, lets do some
- changes to the container, for example, updating it: -->
- LXD はスナップショットの取得とコンテナのスナップショットからのリストアをサポートしています。
- <br />
- スナップショットを作成する前に、コンテナに少し変更を加えてみましょう。例えば、以下のようにアップデートします。
- <pre>lxc exec first -- apt-get update
-lxc exec first -- apt-get dist-upgrade -y
-lxc exec first -- apt-get autoremove --purge -y</pre>
+ container snapshots.
+ <br />
+ Before making a snapshot, lets do some
+ changes to the container, for example, updating it: -->
+ LXD はスナップショットの取得とコンテナのスナップショットからのリストアをサポートしています。
+ <br />
+ スナップショットを作成する前に、コンテナに少し変更を加えてみましょう。例えば、以下のようにアップデートします。
+ <pre>lxc exec first -- apt-get update
+ lxc exec first -- apt-get dist-upgrade -y
+ lxc exec first -- apt-get autoremove --purge -y</pre>
</p>
<p><!-- Now that the container is all updated and
- cleaned, let's make a snapshot called "clean": -->
- 今、コンテナはすべてアップデートされ、クリーンな状態になりました。このスナップショットを "clean" と名づけましょう。
- <pre>lxc snapshot first clean</pre>
+ cleaned, let's make a snapshot called "clean": -->
+ 今、コンテナはすべてアップデートされ、クリーンな状態になりました。このスナップショットを "clean" と名づけましょう。
+ <pre>lxc snapshot first clean</pre>
</p>
<p><!-- Let's break our container: -->
- ここでコンテナを破壊してみましょう。
- <pre>lxc exec first -- rm -Rf /etc /usr</pre>
+ ここでコンテナを破壊してみましょう。
+ <pre>lxc exec first -- rm -Rf /etc /usr</pre>
</p>
<p><!-- Confirm the breakage with (then exit): -->
- 壊れたことを以下のように確認してみます (実行後に exit してください)。
- <pre>lxc exec first -- bash</pre>
+ 壊れたことを以下のように確認してみます (実行後に exit してください)。
+ <pre>lxc exec first -- bash</pre>
</p>
<p><!-- And restore everything to the snapshotted state: -->
- そして、スナップショットの状態へすべてリストアしてみましょう。
- <pre>lxc restore first clean</pre>
+ そして、スナップショットの状態へすべてリストアしてみましょう。
+ <pre>lxc restore first clean</pre>
</p>
<p><!-- And confirm everything's back to normal (then exit): -->
- すべて普通の状態に戻っていることを確認してみましょう (実行後に exit してください)。
- <pre>lxc exec first -- bash</pre>
+ すべて普通の状態に戻っていることを確認してみましょう (実行後に exit してください)。
+ <pre>lxc exec first -- bash</pre>
</p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h5">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b5"
- aria-expanded="false"
- aria-controls="tryit_intro_b5">
- 5. イメージの作成 <!-- Creating images -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b5"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="creating-images">
+ <h3>5. イメージの作成 <!-- Creating images --></h3>
<p><!-- As your probably noticed earlier, LXD is
- image based, that is, all containers must be
- created from either a copy of an existing
- container or from an image. -->
- すでにお分かりのように、LXD はイメージベースです。つまり、すべてのコンテナはイメージか既存のコンテナのコピーのどちらかから作られます。</p>
+ image based, that is, all containers must be
+ created from either a copy of an existing
+ container or from an image. -->
+ すでにお分かりのように、LXD はイメージベースです。つまり、すべてのコンテナはイメージか既存のコンテナのコピーのどちらかから作られます。</p>
<p><!-- You can create new images from an existing
- container or a container snapshot.-->
- あなたは既存のコンテナか、コンテナのスナップショットから新たにイメージを作成できます。</p>
+ container or a container snapshot.-->
+ あなたは既存のコンテナか、コンテナのスナップショットから新たにイメージを作成できます。</p>
<p><!-- To publish our "clean" snapshot from earlier
- as a new image with a user friendly alias of
- "clean-ubuntu", run: -->
- "clean-ubuntu" というユーザフレンドリーなエイリアスを持つ新しいイメージとして、先の "clean" という名前のスナップショットをイメージ化するには、以下のように実行します。
- <pre>lxc publish first/clean --alias clean-ubuntu</pre>
+ as a new image with a user friendly alias of
+ "clean-ubuntu", run: -->
+ "clean-ubuntu" というユーザフレンドリーなエイリアスを持つ新しいイメージとして、先の "clean" という名前のスナップショットをイメージ化するには、以下のように実行します。
+ <pre>lxc publish first/clean --alias clean-ubuntu</pre>
</p>
<p><!-- At which point we won't need our "first"
- container, so just delete it with: -->
- 最初の "first" コンテナが不要であることを示すため、以下のように削除してみましょう。
- <pre>lxc stop first
-lxc delete first</pre>
+ container, so just delete it with: -->
+ 最初の "first" コンテナが不要であることを示すため、以下のように削除してみましょう。
+ <pre>lxc stop first
+ lxc delete first</pre>
</p>
<p><!-- And lastly we can start a new container from
- our image with: -->
- 最後に、作成したイメージから新しいコンテナを起動してみましょう。
- <pre>lxc launch clean-ubuntu second</pre>
+ our image with: -->
+ 最後に、作成したイメージから新しいコンテナを起動してみましょう。
+ <pre>lxc launch clean-ubuntu second</pre>
</p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h6">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b6"
- aria-expanded="false"
- aria-controls="tryit_intro_b6">
- 6. コンテナのファイルへのアクセス <!-- Accessing files from the container -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b6"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="container-files">
+ <h3>6. コンテナのファイルへのアクセス <!-- Accessing files from the container --></h3>
<p><!-- To pull a file from the container you can use
- the "lxc file pull" command: -->
- コンテナからファイルを取得するには、"lxc file pull" コマンドが使えます。
- <pre>lxc file pull second/etc/hosts .</pre>
+ the "lxc file pull" command: -->
+ コンテナからファイルを取得するには、"lxc file pull" コマンドが使えます。
+ <pre>lxc file pull second/etc/hosts .</pre>
</p>
<p><!-- Lets add an entry to it: -->
- 取得したファイルにエントリを追加しましょう。
- <pre>echo "1.2.3.4 my-example" >> hosts</pre>
+ 取得したファイルにエントリを追加しましょう。
+ <pre>echo "1.2.3.4 my-example" >> hosts</pre>
</p>
<p><!-- And push it back where it came from: -->
- 以下のようにしてファイルをコンテナに戻します。
- <pre>lxc file push hosts second/etc/hosts</pre>
+ 以下のようにしてファイルをコンテナに戻します。
+ <pre>lxc file push hosts second/etc/hosts</pre>
</p>
<p><!-- You can also use this mechanism to access log files: -->
- 以下のような方法でログファイルにアクセスすることもできます。
- <pre>lxc file pull second/var/log/syslog - | less</pre>
+ 以下のような方法でログファイルにアクセスすることもできます。
+ <pre>lxc file pull second/var/log/syslog - | less</pre>
</p>
<p><!-- We won't be needing that container anymore,
- so delete it with: -->
- もうこのコンテナが不要であれば、以下のようにして削除しましょう。
- <pre>lxc delete --force second</pre>
+ so delete it with: -->
+ もうこのコンテナが不要であれば、以下のようにして削除しましょう。
+ <pre>lxc delete --force second</pre>
</p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h7">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b7"
- aria-expanded="false"
- aria-controls="tryit_intro_b7">
- 7. リモートのイメージサーバの利用 <!-- Use a remote image server -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b7"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="image-server">
+ <h3>7. リモートのイメージサーバの利用 <!-- Use a remote image server --></h3>
<p><!-- The lxc client tool supports multiple
- "remotes", those remotes can be read-only
- image servers or other LXD hosts. -->
- クライアントツール lxc からは複数の "リモートホスト" が使えます。これらのリモートホストは、読み取り専用のイメージサーバか、他の LXD ホストのどちらかです。</p>
+ "remotes", those remotes can be read-only
+ image servers or other LXD hosts. -->
+ クライアントツール lxc からは複数の "リモートホスト" が使えます。これらのリモートホストは、読み取り専用のイメージサーバか、他の LXD ホストのどちらかです。</p>
<p><!-- LXC upstream runs one such server at
- <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
- which serves a set of automatically generated
- images for various Linux distributions. -->
- LXC 開発元はこのようなサーバを <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a> で運用しています。ここでは、色々な Linux ディストリビューションのイメージを自動的に作成して提供しています。
+ <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a>
+ which serves a set of automatically generated
+ images for various Linux distributions. -->
+ LXC 開発元はこのようなサーバを <a href="https://images.linuxcontainers.org">https://images.linuxcontainers.org</a> で運用しています。ここでは、色々な Linux ディストリビューションのイメージを自動的に作成して提供しています。
</p>
<p><!-- It comes pre-added with default LXD but you
- can remove it or change it if you don't want it. -->
- このサーバはデフォルトで LXD に登録されています。もしこのサーバを使わない場合は、デフォルトの登録を変更したり、削除したりできます。
+ can remove it or change it if you don't want it. -->
+ このサーバはデフォルトで LXD に登録されています。もしこのサーバを使わない場合は、デフォルトの登録を変更したり、削除したりできます。
</p>
<p><!-- You can list the available images with: -->
- 利用可能なイメージのリストは以下のように取得できます。
- <pre>lxc image list images: | less</pre>
+ 利用可能なイメージのリストは以下のように取得できます。
+ <pre>lxc image list images: | less</pre>
</p>
<p><!-- And spawn a new Centos 7 container with: -->
- そして、CentOS 7 コンテナを起動するには、以下のように実行します。
- <pre>lxc launch images:centos/7 third</pre>
+ そして、CentOS 7 コンテナを起動するには、以下のように実行します。
+ <pre>lxc launch images:centos/7 third</pre>
</p>
<p><!-- Confirm it's indeed Centos 7 with: -->
- コンテナが CentOS 7 かどうか確認するには、以下のように実行します。
- <pre>lxc exec third -- cat /etc/redhat-release</pre>
+ コンテナが CentOS 7 かどうか確認するには、以下のように実行します。
+ <pre>lxc exec third -- cat /etc/redhat-release</pre>
</p>
<p><!-- And delete it: -->
- そしてコンテナを削除します。
- <pre>lxc delete -f third</pre>
+ そしてコンテナを削除します。
+ <pre>lxc delete -f third</pre>
</p>
<p><!-- The list of all configured remotes can be
- obtained with: -->
- 設定されたリモートホストの一覧は以下のように取得できます。
- <pre>lxc remote list</pre>
+ obtained with: -->
+ 設定されたリモートホストの一覧は以下のように取得できます。
+ <pre>lxc remote list</pre>
</p>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h8">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b8"
- aria-expanded="false"
- aria-controls="tryit_intro_b8">
- 8. リモートの LXD サーバの操作 <!-- Interact with remote LXD servers -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b8"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="remote-lxd">
+ <h3>8. リモートの LXD サーバの操作 <!-- Interact with remote LXD servers --></h3>
<p><!-- For this step, you'll need a second demo
- session, so open a new one
- <a href="/lxd/try-it/" target="_blank">here</a> -->
- このステップでは、2 つ目のデモセッションが必要となります。そこで新しいセッションを <a href="/lxd/try-it/" target="_blank">ここから</a> 開いてください。</p>
+ session, so open a new one
+ <a href="/lxd/try-it/" target="_blank">here</a> -->
+ このステップでは、2 つ目のデモセッションが必要となります。そこで新しいセッションを <a href="/lxd/try-it/" target="_blank">ここから</a> 開いてください。</p>
<p><!-- Copy/paste the "lxc remote add" command from
- the top of the page of that new session into
- the shell of your old session.
- <br />
- Then confirm the server fingerprint for the remote
- server. -->
- その新しいセッションページのトップにある「コンテナの情報」の "LXD" 部分から以前のセッションのシェルへ "lxc remote add" コマンドをコピー＆ペーストしてください。
- <br />
- そしてリモートサーバのフィンガープリントを確認してください。
- </p>
+ the top of the page of that new session into
+ the shell of your old session.
+ <br />
+ Then confirm the server fingerprint for the remote
+ server. -->
+ その新しいセッションページのトップにある「コンテナの情報」の "LXD" 部分から以前のセッションのシェルへ "lxc remote add" コマンドをコピー＆ペーストしてください。
+ <br />
+ そしてリモートサーバのフィンガープリントを確認してください。
+ </p>
<p><!-- Note that it may take a few seconds for the
- new LXD daemon to listen to the network, just
- retry the command until it answers. -->
- 新しい LXD デーモンは、応答があるまでコマンドをリトライして、ネットワークを LISTEN するまでに数秒かかることがあるかもしれないことに注意してください。</p>
+ new LXD daemon to listen to the network, just
+ retry the command until it answers. -->
+ 新しい LXD デーモンは、応答があるまでコマンドをリトライして、ネットワークを LISTEN するまでに数秒かかることがあるかもしれないことに注意してください。</p>
<p><!-- At this point you can list the remote
- containers with: -->
- この時点で、あなたは以下のようにリモートのコンテナをリスト表示できます。
- <pre>lxc list tryit:</pre></p>
+ containers with: -->
+ この時点で、あなたは以下のようにリモートのコンテナをリスト表示できます。
+ <pre>lxc list tryit:</pre></p>
<p><!-- And its images with: -->
- そして、リモートのイメージをリスト表示できます。
- <pre>lxc image list tryit:</pre>
+ そして、リモートのイメージをリスト表示できます。
+ <pre>lxc image list tryit:</pre>
</p>
<p><!-- Now, lets start a new container on the remote
- LXD using the local image we created earlier. -->
- さあ、先に作成したローカルイメージを使って、リモートの LXD 上で新しいコンテナを起動してみましょう。
- <pre>lxc launch clean-ubuntu tryit:fourth</pre>
+ LXD using the local image we created earlier. -->
+ さあ、先に作成したローカルイメージを使って、リモートの LXD 上で新しいコンテナを起動してみましょう。
+ <pre>lxc launch clean-ubuntu tryit:fourth</pre>
</p>
<p><!-- You now have a container called "fourth"
- running on the remote host "tryit". You can
- spawn a shell inside it with (then exit): -->
- これであなたはリモートホスト "tryit" 上で "fourth" という名前で実行中のコンテナを持っていることになります。以下のようにリモートのコンテナ内でシェルを起動できます (実行後に exit してください)。
- <pre>lxc exec tryit:fourth bash</pre>
+ running on the remote host "tryit". You can
+ spawn a shell inside it with (then exit): -->
+ これであなたはリモートホスト "tryit" 上で "fourth" という名前で実行中のコンテナを持っていることになります。以下のようにリモートのコンテナ内でシェルを起動できます (実行後に exit してください)。
+ <pre>lxc exec tryit:fourth bash</pre>
</p>
<p><!-- Now let's copy that container into a new one
- called "fifth": -->
- このコンテナを新しい "fifth" というコンテナにコピーしてみましょう。
- <pre>lxc copy tryit:fourth tryit:fifth</pre>
+ called "fifth": -->
+ このコンテナを新しい "fifth" というコンテナにコピーしてみましょう。
+ <pre>lxc copy tryit:fourth tryit:fifth</pre>
</p>
<p><!-- And just for fun, move it back to our local
- lxd while renaming it to "sixth": -->
- お遊び感覚で、それをローカルの LXD に "sixth" という名前に変更して移動してみましょう。
- <pre>lxc move tryit:fifth sixth</pre>
+ lxd while renaming it to "sixth": -->
+ お遊び感覚で、それをローカルの LXD に "sixth" という名前に変更して移動してみましょう。
+ <pre>lxc move tryit:fifth sixth</pre>
</p>
<p><!-- And confirm it's all still working (then exit): -->
- そして、それがすべて実行中であることを確認しましょう (実行後に exit してください)。
- <pre>lxc start sixth
-lxc exec sixth -- bash</pre>
+ そして、それがすべて実行中であることを確認しましょう (実行後に exit してください)。
+ <pre>lxc start sixth
+ lxc exec sixth -- bash</pre>
</p>
<p><!-- Then clean everything up: -->
- そして、すべてをクリーンアップするには、以下のように実行します。
- <pre>lxc delete -f sixth
-lxc delete -f tryit:fourth
-lxc image delete clean-ubuntu</pre>
+ そして、すべてをクリーンアップするには、以下のように実行します。
+ <pre>lxc delete -f sixth
+ lxc delete -f tryit:fourth
+ lxc image delete clean-ubuntu</pre>
</div>
- </div>
- </div>
- <div class="panel panel-default">
- <div class="panel-heading" role="tab" id="tryit_intro_h9">
- <h4 class="panel-title">
- <a class="collapsed" role="button"
- data-toggle="collapse"
- data-parent="#tryit_intro" href="#tryit_intro_b9"
- aria-expanded="false"
- aria-controls="tryit_intro_b9">
- 9. さいごに <!-- Conclusion -->
- </a>
- </h4>
- </div>
- <div class="panel-collapse collapse" id="tryit_intro_b9"
- role="tabpanel">
- <div class="panel-body">
+ <div class="tab-content" id="conclusion">
+ <h3>9. さいごに <!-- Conclusion --></h3>
<p><!-- We hope this gave you a good introduction to
- LXD, its capabilities and how easy it is to
- use. -->
- この入門が LXD について、LXD でできること、LXD が簡単に使えることを理解するのに役立つ良い入門となれば幸いです。</p>
+ LXD, its capabilities and how easy it is to
+ use. -->
+ この入門が LXD について、LXD でできること、LXD が簡単に使えることを理解するのに役立つ良い入門となれば幸いです。</p>
<p><!-- You're welcome to use the demo service as
- long as you want to try LXD and play with the
- latest features. -->
- あなたが LXD を使い、最新の機能を体験したいということであれば、このデモサービスを使うことを歓迎します。
- </p>
+ long as you want to try LXD and play with the
+ latest features. -->
+ あなたが LXD を使い、最新の機能を体験したいということであれば、このデモサービスを使うことを歓迎します。
+ </p>
<p>楽しんでください!</p>
</div>
</div>
</div>
- </div>
- </div>
-</div>
-
-<div class="panel panel-danger" id="tryit_error_panel" style="display:none">
- <div class="panel-heading" id="tryit_error_panel_create" style="display:none">新しいコンテナを作成できません <!-- Unable to create a new container --></div>
- <div class="panel-heading" id="tryit_error_panel_access" style="display:none">コンテナにアクセスできません <!-- Unable to access the container --></div>
- <div class="panel-body" id="tryit_error_full" style="display:none">
- サーバが上限に達しています。数分後にもう一度お試しください。<!-- The server is currently full, please try again in a few minutes. -->
+ <div class="p-notification--negative" id="tryit_error_panel" style="display:none">
+ <div class="p-notification__response">
+ <span class="p-notification__status" id="tryit_error_panel_create" style="display:none">新しいコンテナを作成できません <!-- Unable to create a new container --></span>
+ <span class="p-notification__status" id="tryit_error_panel_access" style="display:none">コンテナにアクセスできません <!-- Unable to access the container --></span>
- <br /><br />
+ <div class="panel-body" id="tryit_error_full" style="display:none">
+ <p>サーバが上限に達しています。数分後にもう一度お試しください。<!-- The server is currently full, please try again in a few minutes. --></p>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- やりなおす <!-- Start over -->
- </button>
- </div>
-
- <div class="panel-body" id="tryit_error_quota" style="display:none">
- <!--
- You have reached the maximum number of concurrent sessions,
- please wait for some to expire before starting more of them.
- -->
- 同時に実行できるセッションの最大数に達しました。
- 現在実行中のセッションが期限切れになるまでお待ちください。
- <br /><br />
-
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- やりなおす <!-- Start over -->
- </button>
- </div>
- <div class="panel-body" id="tryit_error_banned" style="display:none">
- <!--
- You have been banned from this service due to a failure to
- respect the terms of service.
- -->
- あなたはサービス利用規約を守らなかったため、サービスの使用を禁止されています。
- </div>
+ <p><button class="p-button tryit_goback" type="button">
+ やりなおす <!-- Start over -->
+ </button></p>
+ </div>
- <div class="panel-body" id="tryit_error_unknown" style="display:none">
- <!--
- An unknown error occured. Please try again in a few minutes.
- -->
- 原因不明のエラーが起きました。数分後にもう一度お試しください。
+ <div class="panel-body" id="tryit_error_quota" style="display:none">
+ <!--
+ You have reached the maximum number of concurrent sessions,
+ please wait for some to expire before starting more of them.
+ -->
+ <p>同時に実行できるセッションの最大数に達しました。
+ 現在実行中のセッションが期限切れになるまでお待ちください。</p>
+
+ <p><button class="p-button tryit_goback" type="button">
+ やりなおす <!-- Start over -->
+ </button></p>
+ </div>
- <br /><br />
+ <div class="panel-body" id="tryit_error_banned" style="display:none">
+ <!--
+ You have been banned from this service due to a failure to
+ respect the terms of service.
+ -->
+ <p>あなたはサービス利用規約を守らなかったため、サービスの使用を禁止されています。</p>
+ </div>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- やりなおす <!-- Start over -->
- </button>
- </div>
+ <div class="panel-body" id="tryit_error_unknown" style="display:none">
+ <!--
+ An unknown error occured. Please try again in a few minutes.
+ -->
+ <p>原因不明のエラーが起きました。数分後にもう一度お試しください。</p>
- <div class="panel-body" id="tryit_error_missing" style="display:none">
- <!--
- The container you're trying to connect to doesn't exist anymore.
- -->
- あなたが接続しようとしているコンテナが存在しません。
+ <p><button class="p-button tryit_goback" type="button">
+ やりなおす <!-- Start over -->
+ </button></p>
+ </div>
- <br /><br />
+ <div class="panel-body" id="tryit_error_missing" style="display:none">
+ <!--
+ The container you're trying to connect to doesn't exist anymore.
+ -->
+ <p>あなたが接続しようとしているコンテナが存在しません。</p>
- <button class="btn btn-default btn-lg tryit_goback" type="button">
- <span aria-hidden="true" class="glyphicon glyphicon-home"></span>
- やりなおす <!-- Start over -->
- </button>
+ <p><button class="p-button tryit_goback" type="button">
+ やりなおす <!-- Start over -->
+ </button></p>
+ </div>
+ </div>
+ </div>
+ </div>
</div>
</div>
From fffddeb224d5574b0c26cb8b5b74853f608b7f10 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Wed, 1 Nov 2017 10:44:28 +0000
Subject: [PATCH 7/8] Remove image from jp-news
---
content/lxc/news.ja.md | 248 ++++++++++++++++++++++++-------------------------
1 file changed, 124 insertions(+), 124 deletions(-)
diff --git a/content/lxc/news.ja.md b/content/lxc/news.ja.md
index e478dd1..bf6366d 100644
--- a/content/lxc/news.ja.md
+++ b/content/lxc/news.ja.md
@@ -1,4 +1,4 @@
-
+
# News
## LXC 1.0.11 リリースのお知らせ <!-- LXC 1.0.11 release announcement --><span class="text-muted">19th of October 2017</span>
This is the eleventh bugfix release for LXC 1.0.
@@ -163,14 +163,14 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.1).
## LXC 2.1 リリースのお知らせ <!-- LXC 2.1 release announcement --><span class="text-muted">2017 年 9 月 5 日<!-- 5th of September 2017 --></span>
<!--
-The LXC team is proud to announce the release of LXC 2.1.
+The LXC team is proud to announce the release of LXC 2.1.
This release contains a lot of new features introduced since the release of LXC 2.0.
-->
LXC チームは LXC 2.1 のリリースをお知らせすることを誇りに思います。
このリリースには LXC 2.0 以降に追加されたたくさんの機能が含まれています。
<!--
-Note that this isn't a LTS release and we'll therefore only be supporting LXC 2.1 for a year.
+Note that this isn't a LTS release and we'll therefore only be supporting LXC 2.1 for a year.
Production environments that require longer term support should remain on LXC 2.0 which is supported until June 2021.
-->
このリリースは LTS リリースではないことに注意してください。LTS リリースではありませんので、LXC 2.1 のサポートは 1 年間のみです。長い期間のサポートが必要なプロダクション環境では 2021 年 6 月までサポートされる LXC 2.0 を使い続けてください。
@@ -178,9 +178,9 @@ Production environments that require longer term support should remain on LXC 2.
## 新機能 <!-- New features -->
### リソース制限のサポート<!-- Resource limit support -->
<!--
-Similar to requesting specific cgroup limits users can specify any limits for any resource
-the underlying kernel is aware of by prefixing the name of the limit with "lxc.prlimit."
-in the container's configuration file. For example, to request a limit on the number of processes
+Similar to requesting specific cgroup limits users can specify any limits for any resource
+the underlying kernel is aware of by prefixing the name of the limit with "lxc.prlimit."
+in the container's configuration file. For example, to request a limit on the number of processes
and a specific nice value the configuration file for the container should contain the entries:
-->
cgroupを使った制限を指定するのと同じように、コンテナの設定ファイル内で、制限名に "lxc.prlimit." というプレフィックスをつけて、カーネルが対応しているすべてのリソースの制限を設定できます。例えば、プロセス数の制限を設定し、同時に nice 値を指定するには、コンテナの設定ファイルで次のように指定します:
@@ -200,29 +200,29 @@ It is now possible to define openvswitch networks as an unprivileged user:
lxc.net.0.name = eth0
<!--
-LXC 2.1. will take care to properly delete the host-side veth device from the
+LXC 2.1. will take care to properly delete the host-side veth device from the
openvswitch database on shutdown.
-->
LXC 2.1 は、シャットダウン時に openvswitch からホスト側の veth デバイスを適切に削除する処理を行います。
### 新たな設定項目 `lxc.cgroup.dir` <!-- New `lxc.cgroup.dir` key -->
<!--
-The `lxc.cgroup.dir` key lets users specify the name of the parent cgroup under
-which the container's cgroup will be created. Setting `lxc.cgroup.dir` will
+The `lxc.cgroup.dir` key lets users specify the name of the parent cgroup under
+which the container's cgroup will be created. Setting `lxc.cgroup.dir` will
override the system-wide setting for `lxc.cgroup.pattern`.
-->
`lxc.cgroup.dir` を設定することで、コンテナ用の cgroup を作成する親となる cgroup 名を指定できるようになりました。`lxc.cgroup.dir` はシステムワイドの設定である `lxc.cgroup.pattern` を上書きします。
<!--
-For example, setting `lxc.cgroup.dir = mycontainers` for a container with `lxc.uts.name = c1`
+For example, setting `lxc.cgroup.dir = mycontainers` for a container with `lxc.uts.name = c1`
will cause LXC to create the cgroups `mycontainers/c1` for all controllers in the cgroup hierarchy.
-->
例えば、`lxc.uts.name = c1` と設定されたコンテナに `lxc.cgroup.dir = mycontainers` と設定すると、LXC は cgroup 階層内のすべてのコントローラで、`mycontainers/c1` という cgroup を作ります。
### hybrid cgroup レイアウトのサポート <!-- Support for hybrid cgroup layout -->
<!--
-Since the advent of cgroup v2 some init systems have decided to allow for a hybrid mode in which
-cgroup v1 per-controller hierarchies can be used simultaneously with an empty cgroup v2 hierarchy.
+Since the advent of cgroup v2 some init systems have decided to allow for a hybrid mode in which
+cgroup v1 per-controller hierarchies can be used simultaneously with an empty cgroup v2 hierarchy.
Systems that use this hybrid mode usually have a cgroup layout similar to this one:
-->
cgroup v2 が導入されてから、一部の init システムでは cgroup v1 のコントローラごとの階層と、空の cgroup v2 階層を同時に使える hybrid モードが使えるようになりました。hybrid モードを使うシステムは、通常は次と同じような cgroup レイアウトになります:
@@ -233,24 +233,24 @@ cgroup v2 が導入されてから、一部の init システムでは cgroup v1
/sys/fs/cgroup/unified
<!--
-Where the mountpoint `/sys/fs/cgroup/unified` usually indicates the presence of a cgroup v2 hierarchy.
-This can be confirmed by testing whether `findmnt | grep cgroup2` returns a matching line.
+Where the mountpoint `/sys/fs/cgroup/unified` usually indicates the presence of a cgroup v2 hierarchy.
+This can be confirmed by testing whether `findmnt | grep cgroup2` returns a matching line.
LXC 2.1 supports this hybrid mode.
-->
マウントポイント `/sys/fs/cgroup/unified` は、通常は cgroup v2 階層の存在を示します。これは `findmnt | grep cgroup2` が一致する行を返すかどうかをテストすることで確認できます。LXC 2.1 はこの hybrid モードをサポートします。
### コンテナが割り当てることができる pty の数を制限する <!-- Limiting the number of ptys a container can allocate -->
<!--
-Setting `lxc.pty.max` will cause LXC to mount the container's devpts with the requested limit
-on the number of useable ptys. For example, setting `lxc.pty.max = 10` will only allow
+Setting `lxc.pty.max` will cause LXC to mount the container's devpts with the requested limit
+on the number of useable ptys. For example, setting `lxc.pty.max = 10` will only allow
the container to allocate `10` ptys. The default setting is `1024`.
-->
`lxc.pty.max` を設定すると、LXC は、使える pty の数に指定した制限を設定した上で、コンテナの devpts をマウントします。例えば、`lxc.pty.max = 10` と設定すると、コンテナは `10` 個の pty だけしか割り当てられません。デフォルト値は `1024` です。
### `bool lxc_config_item_is_supported(const char *key)` API 拡張 <!-- extension -->
<!--
-This function let's users query the liblxc whether a specific configuration item is supported for this library.
-This is particularly useful for embedded users that running versions of liblxc that come with significantly
+This function let's users query the liblxc whether a specific configuration item is supported for this library.
+This is particularly useful for embedded users that running versions of liblxc that come with significantly
less configuration options than the standard liblxc library or liblxc's that have backported new configuration items.
-->
この関数は、特定の設定項目がライブラリでサポートされているかどうかをユーザが問い合わせるための関数です。この関数は、標準的な liblxc ライブラリや、新しい設定項目がバックポートされた liblxc よりもはるかに少ない設定オプションを持つ liblxc のバージョンを実行する組み込みユーザに特に役に立つでしょう。
@@ -286,9 +286,9 @@ These types and functions let users initialize LXC logging. This is useful for u
### `lxc-monitord` が廃止予定に <!-- Deprecation of `lxc-monitord` -->
<!--
-Starting with LXC 2.1 the `lxc-monitord` binary is marked as deprecated.
-It is not required anymore to start daemonized containers. Instead, LXC 2.1 switches to an implementation using
-an abstract unix domain socketpair. This has the advantage of spawning one less processes on container startup which is
+Starting with LXC 2.1 the `lxc-monitord` binary is marked as deprecated.
+It is not required anymore to start daemonized containers. Instead, LXC 2.1 switches to an implementation using
+an abstract unix domain socketpair. This has the advantage of spawning one less processes on container startup which is
important for highly threaded users such as `LXD`.
-->
LXC 2.1 から `lxc-monitord` バイナリは廃止予定になりました。デーモン化されたコンテナの起動には `lxc-monitord` はもう不要です。代わりに、LXC 2.1 では abstract unix ドメインソケットペアを使った実装に切り替えました。これは、`LXD` のような高度にスレッド化されたコンテナの起動において、起動するプロセスがひとつ少なくなるという利点があります。
@@ -300,17 +300,17 @@ Also, testing the new implementation on heavy workloads has shown this solution
### `lxc-copy` は `tmpfs` 上にスナップショットを作ります <!-- `lxc-copy` create snapshots on `tmpfs` -->
<!--
-Place an ephemeral container started with -e flag on a tmpfs.
-Restrictions are that you cannot request the data to be kept while placing the container on a tmpfs,
-that either overlay or aufs backing storage must be used, and that the storage backend of the original
+Place an ephemeral container started with -e flag on a tmpfs.
+Restrictions are that you cannot request the data to be kept while placing the container on a tmpfs,
+that either overlay or aufs backing storage must be used, and that the storage backend of the original
container must be a directory.
-->
`-e` オプションを付けて起動した一時的 (ephemeral) なコンテナは tmpfs 上に置かれます。
tmpfs 上にコンテナを置きながらデータの保存は要求できません。そして、バッキングストアとして overlay か aufs を使わなければならず、オリジナルのコンテナは directory でなくてはいけません。
<!--
-For ephemeral snapshots backed by overlay or aufs filesystems, a fresh tmpfs is mounted over the containers directory
-if the user requests it. This should be the easiest options. Anything else would require us to change the current
+For ephemeral snapshots backed by overlay or aufs filesystems, a fresh tmpfs is mounted over the containers directory
+if the user requests it. This should be the easiest options. Anything else would require us to change the current
mount-layout of overlay and aufs snapshots. A standard overlay or aufs snapshot clone currently has the layout:
-->
overlay もしくは aufs ファイルシステムを使った一時的なスナップショットのために、ユーザの要求に応じて新しい tmpfs がコンテナディレクトリ上にマウントされます。これは最も簡単なオプションです。それ以外の場合は、現在の overlay と aufs スナップショットのマウントレイアウトを変更する必要があります。標準では overlay と aufs のスナップショットクローンのレイアウトは次のようになります:
@@ -325,21 +325,21 @@ overlay もしくは aufs ファイルシステムを使った一時的なスナ
/var/lib/lxc/CLONE_PARENT/rootfs
<!--
-The fact that upperdir and workdir are not placed in a common subfolder under the container directory
-has the consequence that we cannot simply mount a fresh tmpfs under upperdir and workdir
+The fact that upperdir and workdir are not placed in a common subfolder under the container directory
+has the consequence that we cannot simply mount a fresh tmpfs under upperdir and workdir
because overlay expects them to be on the same filesystem.
-->
upperdir と workdir がコンテナディレクトリ以下の共通のサブディレクトリ内に置かれていないということは、新しい tmpfs を単純に upperdir と workdir の下にマウントできないということになります。なぜなら overlayfs はこのふたつが同じファイルシステム上にあることを期待しているからです。
<!--
-Because we mount a fresh tmpfs over the directory of the container the updated /etc/hostname file created
+Because we mount a fresh tmpfs over the directory of the container the updated /etc/hostname file created
during the clone residing in the upperdir (currently named "delta0" by default) will be hidden.
-->
コンテナディレクトリ上に新しい tmpfs をマウントするので、upperdir (現在はデフォルトで "delta0" という名前) 内にクローン中に作成される、更新された `/etc/hostname` ファイルが隠されてしまいます。
<!--
-Hence, if the user requests that the old name is not to be kept for the clone, we recreate this file on the tmpfs.
-This should be all that is required to restore the exact behaviour we would get with a normal clone.
+Hence, if the user requests that the old name is not to be kept for the clone, we recreate this file on the tmpfs.
+This should be all that is required to restore the exact behaviour we would get with a normal clone.
NOTE: If the container is rebooted all changes made to it are lost. This is not easy to prevent since each reboot remounts the rootfs again.
-->
したがって、ユーザが古い名前をクローンで保存しないように要求した場合は、このファイルを tmpfs 上に再作成します。
@@ -348,7 +348,7 @@ NOTE: If the container is rebooted all changes made to it are lost. This is not
## 設定項目名の変更 <!-- Configuration changes -->
<!--
-A lot of configuration keys have been renamed to make the experience of configuring a container much more consistent.
+A lot of configuration keys have been renamed to make the experience of configuring a container much more consistent.
LXC 2.1 ensures that all keys that have subkeys are properly namespaces via the "." syntax.
-->
コンテナの設定がより一貫性を持って行えるように、多数の設定項目の名前が変わりました。
@@ -356,10 +356,10 @@ LXC 2.1 では、すべての設定項目が "." で分けられた適切なネ
### ネットワーク設定 <!-- Network configuration -->
<!--
-The network configuration keys have all been given a new prefix. Some of them have also been renamed.
-From LXC 2.1. onwards network configuration keys using the "lxc.network" prefix are considered deprecated.
-They are replaced by network configuration keys using the new "lxc.net" prefix.
-Furthermore, defining network without indices is marked deprecated.
+The network configuration keys have all been given a new prefix. Some of them have also been renamed.
+From LXC 2.1. onwards network configuration keys using the "lxc.network" prefix are considered deprecated.
+They are replaced by network configuration keys using the new "lxc.net" prefix.
+Furthermore, defining network without indices is marked deprecated.
Consider the following *legacy* network configuration:
-->
ネットワークの設定で、新しいプレフィックスを導入しました。いくつかの項目はリネームされました。
@@ -393,7 +393,7 @@ Would define two distinct networks. Starting with LXC 2.1 this should be replace
lxc.net.1.name = eno1
<!--
-Defining networks only in this manner has the advantage of being consistent and order independent.
+Defining networks only in this manner has the advantage of being consistent and order independent.
This means an equivalent configuration for the two networks would be:
-->
この方法だけで定義を行うと、定義する順序には依存しない、一貫性のある定義になる利点があります。
@@ -410,7 +410,7 @@ This means an equivalent configuration for the two networks would be:
lxc.net.1.name = eno1
<!--
-Note that when using multiple definitions of the same key with the same index only the last one
+Note that when using multiple definitions of the same key with the same index only the last one
will be considered by LXC. This is in line with prior LXC version. For example:
-->
同じインデックスの同じ設定が複数ある場合は、LXC は最後の設定を採用することに注意が必要です。これはこれまでのバージョンの LXC と同じ動作です。例えば:
@@ -477,7 +477,7 @@ The following table lists the legacy configuration keys on the left side and the
### `lxc-update-config` スクリプト <!-- script -->
<!--
-LXC 2.1 comes with a new script `lxc-update-config` which can be used to upgrade existing legacy
+LXC 2.1 comes with a new script `lxc-update-config` which can be used to upgrade existing legacy
LXC configurations to valid LXC 2.1 configurations by simply passing
-->
LXC 2.1 には新しく `lxc-update-config` スクリプトが付属します。これは、以前の設定項目名を LXC 2.1 で有効な設定にアップグレードするのに使えます。次のように実行します
@@ -485,9 +485,9 @@ LXC 2.1 には新しく `lxc-update-config` スクリプトが付属します。
lxc-update-config -c /path/to/config
<!--
-The script will create a backup of the legacy configuration file first.
-The name of the backup config file will by `<original-config-file-name>.backup`.
-The backup is made in case the upgrade does not yield a useable LXC 2.1 config file.
+The script will create a backup of the legacy configuration file first.
+The name of the backup config file will by `<original-config-file-name>.backup`.
+The backup is made in case the upgrade does not yield a useable LXC 2.1 config file.
After creating the backup the script will replace all legacy configuration keys with their new counterparts.
-->
このスクリプトは、最初に現在の設定ファイルのバックアップを取得します。
@@ -497,9 +497,9 @@ After creating the backup the script will replace all legacy configuration keys
## 廃止予定の警告 <!-- Deprecation warnings -->
<!--
-LXC 2.1 intends to be fully backward compatible with respect to pre-2.1 configuration files.
-This specifically means that the presence of any deprecated keys should not prevent the container from being useable.
-However, LXC 2.1 will warn about the presence of any deprecated configuration keys.
+LXC 2.1 intends to be fully backward compatible with respect to pre-2.1 configuration files.
+This specifically means that the presence of any deprecated keys should not prevent the container from being useable.
+However, LXC 2.1 will warn about the presence of any deprecated configuration keys.
On container startup LXC 2.1 will warn *once* with the message:
-->
LXC 2.1 は 2.1 より前の設定ファイルとの完全な下位互換性を持っています。
@@ -509,8 +509,8 @@ LXC 2.1 は 2.1 より前の設定ファイルとの完全な下位互換性を
Please update your configuration file.
<!--
-All users are advised to use the aforementioned `lxc-update-config` script to update their configuration files.
-If the container has logging enabled the log will contain warnings for each detected legacy configuration key.
+All users are advised to use the aforementioned `lxc-update-config` script to update their configuration files.
+If the container has logging enabled the log will contain warnings for each detected legacy configuration key.
This is mostly useful for users who prefer to update their configuration files manually.
-->
すべてのユーザは、前述の `lxc-update-config` スクリプトを使って、設定ファイルを更新することをおすすめします。
@@ -669,13 +669,13 @@ This is mostly useful for users who prefer to update their configuration files m
# ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](https://linuxcontainers.org/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](https://linuxcontainers.org/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.1.
-->
このリリースの tarball は [ダウンロードページ](https://linuxcontainers.org/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.1 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.1) にあります。
@@ -691,9 +691,9 @@ This is the eighth bugfix release for LXC 2.0.
* セキュリティホール <!-- Security fix for -->CVE-2017-5985 の修正
* このバージョンで、すべてのテンプレートでデフォルトのパスワードは設定されなくなりました。代わりに、lxc-attach を使ってユーザの設定を行います。この変更により、(かなり安全性に問題のある) デフォルトユーザを使うように設定された、自動化された環境に影響があるでしょう。
- <!-- All templates have been updated to not set default passwords anymore,
- instead requiring lxc-attach be used to configure users.
- This may affect some automated environments that were relying on our
+ <!-- All templates have been updated to not set default passwords anymore,
+ instead requiring lxc-attach be used to configure users.
+ This may affect some automated environments that were relying on our
default (very much insecure) users. -->
バグ修正 <!-- Bugfixes -->:
@@ -799,13 +799,13 @@ This is the eighth bugfix release for LXC 2.0.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.8.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.8 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable-2.0 ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -866,21 +866,21 @@ This is the tenth bugfix release for LXC 1.0.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.10.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.0.10 のパッケージをリリースするでしょう。
<!--
-Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
-The 1.0 branch will keep being supported until June 2019, but at this point,
+Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
+The 1.0 branch will keep being supported until June 2019, but at this point,
only critical bugfixes and security updates will be backported.
-->
LXC 開発元として、1.0 ユーザには 2.0 LTS リリースへのアップグレードを強くおすすめします。
1.0 ブランチは 2019 年 6 月までサポートが続きます。しかし現時点では、重大なバグフィックスとセキュリティホール対策のみがバックポートされます。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable-1.0 ブランチが [Github](https://github.com/lxc/lxc/tree/stable-1.0) にあります。
@@ -956,13 +956,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.7.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.6 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable-2.0 ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1089,13 +1089,13 @@ This is the sixth bugfix release for LXC 2.0.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.6.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.6 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable-2.0 ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1256,21 +1256,21 @@ This is the ninth bugfix release for LXC 1.0.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.9.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.0.9 のパッケージをリリースするでしょう。
<!--
-Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
-The 1.0 branch will keep being supported until June 2019, but at this point,
+Please note that LXC upstream strongly recommends 1.0 users to upgrade to the 2.0 LTS release.
+The 1.0 branch will keep being supported until June 2019, but at this point,
only critical bugfixes and security updates will be backported.
-->
1.0 ユーザに対して、LXC開発元は 2.0 LTS リリースへのアップグレードを強くおすすめします。
1.0 ブランチは 2019 年 6 月までサポートが続きます。しかし現時点では、重大なバグフィックスとセキュリティホール対策のみがバックポートされます。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable-1.0 ブランチが [Github](https://github.com/lxc/lxc/tree/stable-1.0) にあります。
@@ -1352,13 +1352,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.5.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.5 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1370,7 +1370,7 @@ LXC 1.1 has now reached its end of life.
LXC 1.1 は EOL となりました。
<!--
-This means that the stable-1.1 branch is now closed and we will not be
+This means that the stable-1.1 branch is now closed and we will not be
doing any more bugfix or security releases for this branch.
-->
stable-1.1 ブランチはクローズされ、今後このブランチに対するバグ修正やセキュリティ対策のリリースは行われません。
@@ -1438,13 +1438,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.4.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.4 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1456,7 +1456,7 @@ This is the third bugfix release for LXC 2.0.
このリリースは LXC 2.0 の 3 回目のバグフィックスリリースです。
<!--
-LXC 2.0.3 was released just minutes after LXC 2.0.2 as we spotted an incorrect
+LXC 2.0.3 was released just minutes after LXC 2.0.2 as we spotted an incorrect
AppArmor profile included in the LXC 2.0.2 release tarball.
-->
LXC 2.0.3 は、LXC 2.0.2 に正しくない AppArmor プロファイルが含まれてしまったので、LXC 2.0.2 リリース直後にリリースしました。
@@ -1470,13 +1470,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.3.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.3 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1489,7 +1489,7 @@ This is the second bugfix release for LXC 2.0.
このリリースは LXC 2.0 の 2 回目のバグフィックスリリースです。
<!--
-Please do not use LXC 2.0.2, instead use 2.0.3 which fixes
+Please do not use LXC 2.0.2, instead use 2.0.3 which fixes
an accidental regression in AppArmor coverage.
-->
LXC 2.0.2 は使用せず、代わりに 2.0.3 を使用してください。2.0.3 では AppArmor に関する不具合を修正しています。
@@ -1518,13 +1518,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.2.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.2 のパッケージをリリースするでしょう。(訳注: 前述のように 2.0.2 の代わりに 2.0.3 を使用してください)
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1580,13 +1580,13 @@ The main bugfixes in this release are:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.1.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.1 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-2.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチが [Github](https://github.com/lxc/lxc/tree/stable-2.0) にあります。
@@ -1685,8 +1685,8 @@ This release was made possible by contributions (720 commits) from a total of 96
* lxc.hook.post-stop が失敗した場合は、コンテナがリブートが失敗するようになりました <!-- lxc.hook.post-stop failures are now fatal to container reboots -->
<!--
-Note that several commands have been significantly reworked in this release.
-We don't consider our command line tools as stable ABI so you may need to test and adapt your scripts,
+Note that several commands have been significantly reworked in this release.
+We don't consider our command line tools as stable ABI so you may need to test and adapt your scripts,
or better, port them to use our stable C API or one of its bindings.
-->
このリリースで、コマンドの中には大きく作り直されたものがあります。
@@ -1696,8 +1696,8 @@ or better, port them to use our stable C API or one of its bindings.
### 廃止予定の警告 <!-- Deprecation warnings -->
<!--
-The "lxc-clone" and "lxc-start-ephemeral" commands are now considered deprecated and to be replaced by the new lxc-copy.
-Those commands can still be built by using the \-\-enable-legacy flag, however note that they will print a warning when used
+The "lxc-clone" and "lxc-start-ephemeral" commands are now considered deprecated and to be replaced by the new lxc-copy.
+Those commands can still be built by using the \-\-enable-legacy flag, however note that they will print a warning when used
and that they will be removed from upcoming LXC releases.
-->
"lxc-clone" と "lxc-start-ephemeral" コマンドは、"lxc-copy" に置き換えられ、将来廃止の予定です。
@@ -1705,8 +1705,8 @@ and that they will be removed from upcoming LXC releases.
### サポート <!-- Support -->
<!--
-This is the second LXC Long Term Support release which we will be supporting until the 1st of June 2021.
-LXC 1.0, our previous Long Term Support release, is still supported until the 1st of June 2019.
+This is the second LXC Long Term Support release which we will be supporting until the 1st of June 2021.
+LXC 1.0, our previous Long Term Support release, is still supported until the 1st of June 2019.
And lastly, the previous stable release, LXC 1.1 will go end of life on the 1st of September 2016.
-->
これは 2 度目の LXC の長期サポートリリースであり、2021 年 6 月 1 日までサポートされます。
@@ -1715,13 +1715,13 @@ And lastly, the previous stable release, LXC 1.1 will go end of life on the 1st
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 2.0.0.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 2.0.0 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our master branch is on [Github](https://github.com/lxc/lxc/tree/master).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、master ブランチが [Github](https://github.com/lxc/lxc/tree/master) にあります。
@@ -1933,13 +1933,13 @@ Those stable fixes were brought to you by 59 individual contributors.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.8.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.0.8 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチは [Github](https://github.com/lxc/lxc/tree/stable-1.0) にあります。
@@ -1978,13 +1978,13 @@ Init スクリプト<!-- Init scripts -->:
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.5.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.1.5 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチ (stable-1.1) は [Github](https://github.com/lxc/lxc/tree/stable-1.1) にあります。
@@ -2070,13 +2070,13 @@ Those stable fixes were brought to you by 14 individual contributors.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.4.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.1.4 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチ (stable-1.1) は [Github](https://github.com/lxc/lxc/tree/stable-1.1) にあります。
@@ -2094,11 +2094,11 @@ This is the third bugfix release for LXC 1.1.
* セキュリティホール CVE-2015-1331 の修正 <!-- Security fix for CVE-2015-1331 -->
* セキュリティホール CVE-2015-1334 の修正 <!-- Security fix for CVE-2015-1334 -->
- * LXC 1.1 で生じた LXC 1.0 との ABI の非互換性に関する修正を行いました <!-- Fix an ABI regression in LXC 1.1 compared to LXC 1.0. -->
+ * LXC 1.1 で生じた LXC 1.0 との ABI の非互換性に関する修正を行いました <!-- Fix an ABI regression in LXC 1.1 compared to LXC 1.0. -->
大変申し訳ないことですが、この修正は LXC 1.1.0、1.1.1、1.1.2 でビルドしたバイナリは LXC 1.1.3 で再度ビルドする必要があることを意味します。しかし、この修正は LXC 1.0 とそのバグフィックスリリースに対するバイナリとの後方互換性を損なうよりも望ましいことです。
<!--
Fixing this unfortunately means that binaries built against LXC
- 1.1.0, 1.1.1 and 1.1.2 will need rebuilding against LXC 1.1.3.
+ 1.1.0, 1.1.1 and 1.1.2 will need rebuilding against LXC 1.1.3.
This is however preferable to not having backward compatibility with
binaries built for LXC 1.0 and its bugfix releases.
-->
@@ -2161,13 +2161,13 @@ Those stable fixes were brought to you by 31 individual contributors.
### ダウンロード<!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.3.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.1.3 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチ (stable-1.1) は [Github](https://github.com/lxc/lxc/tree/stable-1.1) にあります。
@@ -2200,13 +2200,13 @@ Those stable fixes were brought to you by 9 individual contributors.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.2.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.1.2 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチ (stable-1.1) は [Github](https://github.com/lxc/lxc/tree/stable-1.1) にあります。
@@ -2241,13 +2241,13 @@ Those stable fixes were brought to you by 13 individual contributors.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.1.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.1.1 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチ (stable-1.1) は [Github](https://github.com/lxc/lxc/tree/stable-1.1) にあります。
@@ -2257,40 +2257,40 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.1).
<!-- The LXC team is pleased to announce the release of LXC 1.1. -->
LXC チームは LXC 1.1 のリリースを発表しました。
-<!-- This release will be supported until January 2016 or 2 months after the next release of LXC,
+<!-- This release will be supported until January 2016 or 2 months after the next release of LXC,
whichever comes last. -->
このリリースは 2016 年 1 月か、その時点で LXC の次のリリース (1.2) がなされていない場合は、次のリリースの 2 ヶ月後までサポートされます。
<!--
-If you need a long-term supported version of LXC for use in production, we still strongly recommend
+If you need a long-term supported version of LXC for use in production, we still strongly recommend
you stick to LXC 1.0 which is supported with frequent stable releases until April 2019.
-->
プロダクション環境での長期間のサポートが必要であれば、2019 年 4 月まで安定版リリースとしてサポートされる LXC 1.0 を使い続けることを強くおすすめします。
<!--
-While not strictly required, it is recommended that LXC 1.1 be used with cgmanager 0.35 (or higher)
+While not strictly required, it is recommended that LXC 1.1 be used with cgmanager 0.35 (or higher)
and lxcfs 0.5 (or higher).
-->
一方でそこまでの厳密さが不要であれば、LXC 1.1 を cgmanager 0.35 以降、lxcfs 0.5 以降と一緒に使うこともおすすめです。
### 注目の新機能 <!-- Highlights -->
<!--
-LXC 1.1 introduces checkpoint/restore support for containers through CRIU.
-This allows to serialize the container running state to disk, for live migration or for later local restoration
+LXC 1.1 introduces checkpoint/restore support for containers through CRIU.
+This allows to serialize the container running state to disk, for live migration or for later local restoration
of the container.
-->
LXC 1.1 は CRIU を使ったコンテナのチェックポイント・リストアの機能を新たに導入しました。
<!--
-Support for running systemd as the init system inside the container was also greatly improved
-and should now work by default both for privileged and unprivileged containers when combined
+Support for running systemd as the init system inside the container was also greatly improved
+and should now work by default both for privileged and unprivileged containers when combined
with lxcfs and a recent systemd.
-->
コンテナ内の init として systemd の実行のサポートも大きな改良点です。lxcfs と最新の systemd の組み合わせで、特権、非特権の両方のコンテナが動作するでしょう。
<!--
-Init scripts have now all been updated to provide the same feature set, which means that a lxcbr0 bridge
-with a DHCP and DNS server (dnsmasq) is now the default for anyone using LXC.
+Init scripts have now all been updated to provide the same feature set, which means that a lxcbr0 bridge
+with a DHCP and DNS server (dnsmasq) is now the default for anyone using LXC.
We currently provide init scripts for systemd, sysvinit and upstart.
-->
init スクリプトが更新されました。これにより LXC を使ういかなるシステムでも、DHCP サーバと DNS サーバ機能を dnsmasq によって提供する lxcbr0 ブリッジがデフォルトとなり、同じように動くようになりました。現時点で systemd、sysvinit、upstart 向けの init スクリプトを提供しています。
@@ -2344,12 +2344,12 @@ init スクリプトが更新されました。これにより LXC を使うい
* templates: 全てのテンプレートで lxc.mount.auto = cgroup:mixed proc:mixed sys:mixed を使うようになりました (安全なデフォルト設定です) <!-- All templates now use lxc.mount.auto = cgroup:mixed proc:mixed sys:mixed (safe default configuration) -->
### ダウンロード<!-- Downloads -->
-<!-- The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+<!-- The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.1.0, unless they decide to stick to the long term 1.0 release. -->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションが長期サポートの 1.0 リリースの採用を続ける決定をしない場合は、すぐに LXC 1.1.0 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our master branch is on [Github](https://github.com/lxc/lxc/tree/master).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、master ブランチは [Github](https://github.com/lxc/lxc/tree/master) にあります。
@@ -2453,13 +2453,13 @@ Those stable fixes were brought to you by 27 individual contributors.
### ダウンロード <!-- Downloads -->
<!--
-The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
+The release tarballs may be found on our [download page](/lxc/downloads/) and we expect most distributions
will very soon ship a packaged version of LXC 1.0.7.
-->
このリリースの tarball は [ダウンロードページ](/lxc/downloads/) から取得できます。そして、各ディストリビューションがすぐに LXC 1.0.7 のパッケージをリリースするでしょう。
<!--
-Should you be interested in individual changes or just looking at the detailed development history,
+Should you be interested in individual changes or just looking at the detailed development history,
our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
-->
個々の変更点に興味がある場合、そして開発の履歴を見たい場合、stable ブランチは [Github](https://github.com/lxc/lxc/tree/stable-1.0) にあります。
@@ -2478,7 +2478,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- rootfs_is_blockdev: don't run if no rootfs is specified -->rootfs_is_blockdev: rootfs が指定されていないときには実行されないようにしました (訳注: rootfs が指定されていない場合はストレージバックエンドがブロックデバイスかどうかチェックを行う処理を実行しないようにしました)
* <!-- confile: sanity-check netdev->type before setting
netdev->priv elements -->confile: netdev->priv を設定する前に netdev->type のチェックを行うようにしました
@@ -2632,7 +2632,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- core: Fix unprivileged containers to work with recent
kernels. -->core: 最近のカーネルで非特権コンテナが動作するように修正しました(訳注: 最近のカーネル = 3.15.1 or 3.14.8 以降)
* <!-- core: Fix building with -Werror=maybe-uninitialized. -->core: -Werror=maybe-uninitialized を付けた時のビルドの問題を修正しました
@@ -2694,7 +2694,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- core: Don't call nih_dbus_setup for cgmanager as it's
only relevant when using a nih main loop, which we're not. -->core: cgmanager に対して nih_dbus_setup を呼ばないようにしました。これはnihのメインループを使うときだけ使うのが適切なものでしたが、lxc では使っていないためです。
* <!-- core: Fix uncheck realloc in lxc_info. (found by cppcheck) -->core: lxc_infoでreallocのチェックをしていなかったのを修正しました。(cppcheckで発見)
@@ -2725,7 +2725,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
* <!-- core: Use the same ifndef/define format for all headers. -->core: 全てのヘッダファイルでの ifndef/define のフォーマットを統一しました。
* <!-- core: Fix bashism in lxc-devsetup. -->core: lxc-devsetup での bashism (bash特有の機能) を修正しました。
* <!-- core: Fix a null check after dereference (identified by
- coverity). -->ポインタの値を参照した後の null チェックの修正を行いました (coverity で検出)
+ coverity). -->ポインタの値を参照した後の null チェックの修正を行いました (coverity で検出)
* <!-- core: Export bdev_specs so that API users can actually use the
functions taking it as an argument. -->core: bdev_specs 構造体を export しました。これにより API を使う場合に引数として関数で使うことができるようになりました。
* <!-- core: Don't destroy the container until we've made sure
@@ -2817,7 +2817,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- core: Always initialize netpipe in lxc_spawn. -->core: lxc_spawn 中で常に netpipe を初期化するようにしました (訳注: 非特権コンテナのリブート時に存在しないパイプに対してメッセージを送ることのないように lxc_spawn 中でパイプを初期化するように修正されています)
* <!-- core: Move lxc-monitord.log to LOGPATH instead of LXCPATH. -->core: lxc-monitord.log が LXCPATH でなく LOGPATH に出力されるようになりました
* <!-- core: Make monitord more resilient to unexpected
@@ -2872,7 +2872,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
* <!-- tests: Bump timeouts to fix occasional failures on slow
ARM builders. -->tests: 遅い ARM での失敗のケースの修正としてタイムアウト値を増やしました
* <!-- tests: Always propagate http_proxy and https_proxy. -->tests: 常に http_proxy と https_proxy の値を使用するようにしました
-
+
### <!-- Downloads -->ダウンロード
@@ -2897,7 +2897,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- core: Fix parsing lxc.netwotk.type = none -->core: lxc.network.type = none を指定した場合の不具合を修正しました
* <!-- core: Fix race on shutdown causing SIGPIPE being sent to
the caller -->core: シャットダウン時にコマンドの呼び出し元に SIGPIPE が送られないように修正しました
@@ -2935,7 +2935,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
* <!-- fedora template: Use a sane default for localtime -->fedora template: 適切なデフォルトの localtime を使うようにしました
* <!-- fedora template: Fix building i686 containers on x86_64 -->fedora template: x86_64 環境上での i686 コンテナの作成時の不具合を修正しました
* <!-- opensuse template: Fix syntax error -->opensuse template: 文法エラーを修正しました
-
+
### <!-- Downloads -->ダウンロード
@@ -2959,7 +2959,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
### <!-- Changes -->変更点
-
+
* <!-- core: Detect the use of rshared / and properly work
around it. This fixes LXC on systemd systems where the mount
table would be duplicated in the container and
@@ -3030,7 +3030,7 @@ our stable branch is on [Github](https://github.com/lxc/lxc/tree/stable-1.0).
tests: lxc-test-concurrent 中に hang する可能性があったのを修正しました
* <!-- upstart: Don't forward requests for LXC_DOMAIN (dnsmasq) -->
upstart: LXC_DOMAIN で指定されたものに対するリクエストを転送しなくなりました (dnsmasq)
-
+
### <!-- Downloads -->ダウンロード
From 9cffca5c25b05594d3b6a8f46fd495af63f92935 Mon Sep 17 00:00:00 2001
From: Anthony Dillon <me at anthonydillon.com>
Date: Wed, 1 Nov 2017 10:47:37 +0000
Subject: [PATCH 8/8] Remove bootstraps JS
---
templates/common/base.tpl.html | 1 -
1 file changed, 1 deletion(-)
diff --git a/templates/common/base.tpl.html b/templates/common/base.tpl.html
index f3c403c..5223e99 100644
--- a/templates/common/base.tpl.html
+++ b/templates/common/base.tpl.html
@@ -54,7 +54,6 @@
{% include ["common/footer." + page_language[0] + ".tpl.html", "common/footer.tpl.html"] %}
<script src="/static/js/jquery.min.js"></script>
- <script src="/static/js/bootstrap.min.js"></script>
</div>
</body>
</html>
More information about the lxc-devel
mailing list