[lxc-devel] [lxc/master] doc: Update Korean lxc-attach(1) and lxc-copy(1), Improve lxc-unshare(1)
The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/lxc/pull/871 This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === From 273b3837cec1585db80007ed5e333e8c29ae98f8 Mon Sep 17 00:00:00 2001 From: Sungbae YooDate: Fri, 4 Mar 2016 11:25:16 +0900 Subject: [PATCH 1/3] doc: add copy hook explanation to Korean lxc-copy(1) Update for commit cc0607a Signed-off-by: Sungbae Yoo --- doc/ko/lxc-copy.sgml.in | 28 doc/ko/lxc.container.conf.sgml.in | 7 --- 2 files changed, 32 insertions(+), 3 deletions(-) diff --git a/doc/ko/lxc-copy.sgml.in b/doc/ko/lxc-copy.sgml.in index d0ed1fe..25f421d 100644 --- a/doc/ko/lxc-copy.sgml.in +++ b/doc/ko/lxc-copy.sgml.in @@ -64,6 +64,7 @@ by Sungbae Yoo -K, --keepdata -M, --keepmac -L, --fssize size [unit] + -- hook arguments lxc-copy @@ -77,6 +78,7 @@ by Sungbae Yoo -K, --keepdata -M, --keepmac -L, --fssize size [unit] + -- hook arguments lxc-copy @@ -335,6 +337,32 @@ by Sungbae Yoo + +복사 훅 + + + 복사되는 컨테이너에 lxc.hook.clone가 하나 이상 지정되어 있다면, 지정한 훅들은 새로운 컨테이너를 위해 실핼될 것이다. + clone 훅에게 넘겨지는 처음 3개 인자들은 컨테이너 이름, 섹션 ('lxc'), 훅의 종류 ('clone')이 될 것이다. + lxc-copy에 넘겨지는 추가 인자들은 훅 프로그램에 4번째 인자부터 넘겨지기 시작한다. + LXC_ROOTFS_MOUNT 환경 변수는 컨테이너의 루트 파일시스템이 마운트되어 있는 경로를 담고 있다. + 설정 파일의 경로 이름은 LXC_CONFIG_FILE에, 새 컨테이너의 이름은 LXC_NAME에, 원본 컨테이너의 이름은 LXC_SRC_NAME에, 그리고 루트 파일시스템이 위치하고 있는 경로나 디바이스는 LXC_ROOTFS_PATH에 각각 담겨 있다. + + + diff --git a/doc/ko/lxc.container.conf.sgml.in b/doc/ko/lxc.container.conf.sgml.in index 7ea67c0..cb0bc27 100644 --- a/doc/ko/lxc.container.conf.sgml.in +++ b/doc/ko/lxc.container.conf.sgml.in @@ -1480,11 +1480,12 @@ proc proc proc nodev,noexec,nosuid 0 0 syscall. Any directory suffices, the default should generally work. --> - 루트파일시스템을 변경하기 전에, lxc.rootfs을 어디에 재귀적으로 바인드할지 정한다. 이는 다음 시스템콜의 성공을 보장한다. + 루트 파일시스템을 변경하기 전에, lxc.rootfs을 어디에 재귀적으로 바인드할지 정한다. 이는 pivot_root 8 - + + 시스템 콜의 성공을 보장한다. 어떤 디렉토리도 좋으며, 기본값으로도 보통 동작할 것이다. @@ -1869,7 +1870,7 @@ mknod errno 0 LXC_ROOTFS_MOUNT: 마운트될 루트 파일시스템의 경로 LXC_CONFIG_FILE: 컨테이너 설정파일의 경로 LXC_SRC_NAME: clone 훅의 경우, 원본 컨테이너의 이름 - LXC_ROOTFS_PATH: 컨테이너의 lxc.rootfs 항목. 이 것은 마운트된 루트 파일시스템을 나타내지 않음에 주의해야한다. 그 목적을 위해서는 LXC_ROOTFS_MOUNT를 사용해야 한다. + LXC_ROOTFS_PATH: 컨테이너의 lxc.rootfs 항목. 이 것은 마운트된 루트 파일시스템을 가리키는 것이 아님에 주의해야한다. 그 목적을 위해서는 LXC_ROOTFS_MOUNT를 사용해야 한다. From aef119a3fa1054044f405c660008cb7ababbba08 Mon Sep 17 00:00:00 2001 From: Sungbae Yoo Date: Fri, 4 Mar 2016 11:55:03 +0900 Subject: [PATCH 2/3] doc: improve Korean lxc-attach(1) Explain that the pipe symbol needs to be escaped for -e and -s. Update for commit 759d521 Signed-off-by: Sungbae Yoo --- doc/ko/lxc-attach.sgml.in | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/ko/lxc-attach.sgml.in b/doc/ko/lxc-attach.sgml.in index b863dd7..db5ebff 100644 --- a/doc/ko/lxc-attach.sgml.in +++ b/doc/ko/lxc-attach.sgml.in @@ -172,9 +172,12 @@ by Sungbae Yoo CGROUP|LSM. Allowed values are CGROUP, CAP and LSM representing cgroup, capabilities and - restriction privileges respectively. + restriction privileges respectively. (The pipe symbol needs to be escaped, + e.g. CGROUP\|LSM or quoted, e.g. + "CGROUP|LSM".) --> 만약 모든 privilege를 얻고 싶지 않을 경우에는 CGROUP|LSM와 같이 파이프(|)로 구분된 리스트를 사용할 수 있다. 허용되는 값은 CGROUP、CAP、LSM이다. 각각 cgroup, capability, MAC label을 나타낸다. +(파이프 기호는 CGROUP\|LSM처럼 \로 처리를 해주거나, "CGROUP|LSM"처럼 따옴표를 붙여야 한다.) 붙일 네임스페이스를 지정한다. NETWORK|IPC와 같이 파이프(|)로 구분된 리스트를 사용할 수 있다. 허용되는 값은 MOUNT, PID, UTSNAME, IPC, USER , NETWORK이다. 이를 사용하여, 컨테이너의 네트워크 네임스페이스를 사용하면서도 다른 네임스페이스는 호스트의 것을 그대로 사용하는 등의 조작이 가능하다. +(파이프 기호는 MOUNT\|PID처럼 \로 처리를 해주거나, "MOUNT|PID"처럼 따옴표를 붙여야 한다.) アタッチする名前空間を、パイプでつなげたリストで指定します。 例えば NETWORK|IPC のようにです。 指定できる値は MOUNT、PID、UTSNAME、IPC、USER 、NETWORK です。 これにより、プロセスのコンテキストを変更することができます。 例えば、コンテナのネットワーク名前空間だけを変更し、他の名前空間をホストのものと同じものに保ったままにするというようなことです。 +(パイプ記号を MOUNT\|PID のようにエスケー +プするか、"MOUNT|PID" のように引用符号を付ける必要が>あります。) diff --git a/doc/ko/lxc-unshare.sgml.in
[lxc-devel] LXD live migration fail, help
I failed simple live migration 2.0.0.0 beta4. so I installed source code, now LXD version is* 2.0.0.rc1.* I create a one container (name: psychosomatic-joella) and apply profile 'migratable' to container and copy profile to remote server . and then I tried Live migration again, but still fail. also still error logging as follow : lxc 20160304022641.124 ERRORlxc_criu - criu.c:criu_version_ok:348 - must have criu 1.9 or greater to checkpoint/restore Why? LXD still ask a criu 1.9 or greater ??? *Is there any way to criu upgrade to 1.9??? where can I get criu 1.9??* Thanks in advance. ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [lxc/master] cgfs: stab in the dark
The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/lxc/pull/869 This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === Tycho is reporting errors looking like: lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:890 - Could not find writable mount point for cgroup hierarchy 13 while trying to create cgroup. lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/ lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids//init.scope [...] lxc 20160303090016.270 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids/ on occasional migration runs. I've not reproduced this, but it looks like cgroup_rmdir is trying to delete '/'. This isn't terrible, as any populated cgroups cannot be removed, and we don't enforce removal by killing tasks :) But we could race with someone doing mkdir cgroup move task > cgroup So catch any case where it looks like we have not properly set a cgroup path, and don't remove null or / cgroup. Signed-off-by: Serge HallynFrom f69a4312e618bbf479525f771d323246e76d523d Mon Sep 17 00:00:00 2001 From: Serge Hallyn Date: Thu, 3 Mar 2016 09:21:16 -0800 Subject: [PATCH] cgfs: stab in the dark Tycho is reporting errors looking like: lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:890 - Could not find writable mount point for cgroup hierarchy 13 while trying to create cgroup. lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/ lxc 20160303090016.268 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids//init.scope [...] lxc 20160303090016.270 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:210 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids/ on occasional migration runs. I've not reproduced this, but it looks like cgroup_rmdir is trying to delete '/'. This isn't terrible, as any populated cgroups cannot be removed, and we don't enforce removal by killing tasks :) But we could race with someone doing mkdir cgroup move task > cgroup So catch any case where it looks like we have not properly set a cgroup path, and don't remove null or / cgroup. Signed-off-by: Serge Hallyn --- src/lxc/cgfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lxc/cgfs.c b/src/lxc/cgfs.c index 05e7bcf..f7a3c72 100644 --- a/src/lxc/cgfs.c +++ b/src/lxc/cgfs.c @@ -1245,7 +1245,7 @@ void lxc_cgroup_process_info_free_and_remove(struct cgroup_process_info *info, s if (!info) return; next = info->next; - { + if (info->cgroup_path && strcmp(info->cgroup_path, "/") != 0) { struct cgroup_mount_point *mp = info->designated_mount_point; if (!mp) mp = lxc_cgroup_find_mount_point(info->hierarchy, info->cgroup_path, true); ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] Passed: lxc/lxc#1788 (lxc-2.0.0.rc5 - b5e6a37)
Build Update for lxc/lxc - Build: #1788 Status: Passed Duration: 1 minute and 20 seconds Commit: b5e6a37 (lxc-2.0.0.rc5) Author: Stéphane Graber Message: change version to 2.0.0.rc5 in configure.ac Signed-off-by: Stéphane GraberView the changeset: https://github.com/lxc/lxc/compare/lxc-2.0.0.rc5 View the full build log and details: https://travis-ci.org/lxc/lxc/builds/113436275 -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
Re: [lxc-devel] Contributions to LXC now prefered as Github pull-requests
On Mon, Feb 01, 2016 at 12:43:21PM +0100, Stéphane Graber wrote: > Hello, > > For a long time, Serge and I have been preferring LXC contributions to > be sent through the mailing-list kernel-style. > > This has been working reasonably well for us though lately I've been > lagging behind a bit in mailing-list reviews, leading to occasional > conflicts and regressions. > > For LXD and LXCFS we've been preferring contributions be sent through > pull requests on Github where we have integration with our Jenkins > testsuite. After some discussion with Serge a couple of days ago at > FOSDEM, we've decided that we should apply the same policy for LXC going > forward. > > That means that from now on, the preferred way of contributing to LXC is > through Github pull requests again the master branch. We will still > accept patches sent to the list for those of you who don't wish to > register on Github, but those will typically be lower priority for us > than those sent through Github. > > > I'm adding a couple more sanity checks to Jenkins today and also adding > e-mail notifications of new pull requests so that pull requests sent > through Github result in an e-mall on the list with the appropriate > subject line and description as well as an attached patch of the change. > > -- > Stéphane Graber > Ubuntu developer > http://www.ubuntu.com Hey everyone, So we've now been doing this for a month and I figured it'd be a good time to get some feedback. How has the new process been working for you? Is it faster and easier to get changes into LXC or has Github been a problem with you and slowing you down or causing you to re-consider sending changes upstream? On my side, it seems like we've been significantly faster at doing reviews and getting stuff merged, part of this is thanks to Github making it easy to review and merge stuff but another part is thanks to Christian who's joined Serge, Dwight and I as committer to the project. Being able to trivially (and for committers, automatically) get Jenkins to run all our tests against proposed changes is very convenient and has caught a number of issues we wouldn't have seen through normal review, so overall I'm quite happy with the chaage. -- Stéphane Graber Ubuntu developer http://www.ubuntu.com signature.asc Description: PGP signature ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [lxc/lxc] b5e6a3: change version to 2.0.0.rc5 in configure.ac
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: b5e6a3768c8d8d79f367439e08aa8d7f1183be2d https://github.com/lxc/lxc/commit/b5e6a3768c8d8d79f367439e08aa8d7f1183be2d Author: Stéphane GraberDate: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M configure.ac Log Message: --- change version to 2.0.0.rc5 in configure.ac Signed-off-by: Stéphane Graber ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [lxc/lxc]
Branch: refs/tags/lxc-2.0.0.rc5 Home: https://github.com/lxc/lxc ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [lxc/lxc] 22926b: console.{c.h}: add/improve documentation
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: 22926b39719eee63155a0942b17539e291612e17 https://github.com/lxc/lxc/commit/22926b39719eee63155a0942b17539e291612e17 Author: Christian BraunerDate: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M src/lxc/console.c M src/lxc/console.h Log Message: --- console.{c.h}: add/improve documentation Signed-off-by: Christian Brauner Commit: e31d0f819e5766fe5a367e11e404c94a29ae3b21 https://github.com/lxc/lxc/commit/e31d0f819e5766fe5a367e11e404c94a29ae3b21 Author: Stéphane Graber Date: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M src/lxc/console.c M src/lxc/console.h Log Message: --- Merge pull request #868 from brauner/bugfix_branch console.{c.h}: add/improve documentation Compare: https://github.com/lxc/lxc/compare/c9f5f3598e54...e31d0f819e57___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [linuxcontainers.org/master] Update Japanese instructions for current LXD
The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/linuxcontainers.org/pull/156 This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === * Update for commit b7dd5f7 * Fix html in English try-it Signed-off-by: KATOH YasufumiFrom 781ef6fd189f13d1d6bc0b860ca6f8ba71f21236 Mon Sep 17 00:00:00 2001 From: KATOH Yasufumi Date: Thu, 3 Mar 2016 18:06:42 +0900 Subject: [PATCH] Update Japanese instructions for current LXD * Update for commit b7dd5f7 * Fix html in English try-it Signed-off-by: KATOH Yasufumi --- content/lxd/getting-started-cli.ja.md | 40 --- content/lxd/try-it.html | 3 ++- content/lxd/try-it.ja.html| 36 +-- 3 files changed, 41 insertions(+), 38 deletions(-) diff --git a/content/lxd/getting-started-cli.ja.md b/content/lxd/getting-started-cli.ja.md index 16d11ba..4687401 100644 --- a/content/lxd/getting-started-cli.ja.md +++ b/content/lxd/getting-started-cli.ja.md @@ -98,7 +98,7 @@ There are three ways to feed that image store: イメージストアにイメージを取得する方法は 3 つあります: 1. イメージサーバとしてリモートの LXD を使う - 2. lxd-images スクリプトを使って、LXD 用でないものからイメージをインポートする + 2. ビルトインされているイメージ用リモートサーバを使う 3. 以下のように手動でインポートする lxc image import --alias @@ -109,8 +109,8 @@ Using a remote image server is as simple as adding it as a remote and just using --> リモートのイメージサーバを使うと、リモートサーバとして追加してそれを使うだけですので、とても簡単です: -lxc remote add images images.linuxcontainers.org -lxc launch images:centos/7/amd64 centos +lxc remote add images 1.2.3.4 +lxc launch images:image-name your-container +## ビルトインされているイメージ用リモートサーバを使う -lxd-images は python スクリプトで、LXD 用でないイメージサーバからイメージを取得してインポートできます。 +LXD にはデフォルトでイメージを提供するリモートサーバが 3 つ登録されています: - -現時点では、2 つのソースをサポートしています: - - 1. 手元に存在する busyboxy バイナリから busybox イメージを作成する (テスト用) - 2. 公式の feed から取得した Ubuntu クラウドイメージ - - -新しいイメージの取得は以下のように行います: - -lxd-images import busybox --alias busybox -lxd-images import ubuntu --alias ubuntu + 1. ubuntu: (stable Ubuntu イメージ用 ) + 2. ubuntu-daily: (daily Ubuntu イメージ用 ) + 3. images: (その他の多数のディストリビューション用 ) -その後、コンテナを起動するために単にそのイメージを使うだけです: +これらのビルトインのリモートサーバからコンテナを起動するには、以下のように実行します: -lxc launch busybox my-busybox -lxc launch ubuntu my-ubuntu +lxc launch ubuntu:14.04 my-ubuntu +lxc launch ubuntu-daily:16.04 my-ubuntu-dev +lxc launch images:centos/6/amd64 my-centos ## 手動でイメージをインポートする - LXD はイメージベースです。ローカルのイメージリストを以下のように取得できます。 - lxc image list + + LXD はイメージベースです。しかし、デフォルトでは以下のコマンドの結果のように、イメージはロードされていません: lxc image list - - それでは "ubuntu" イメージを使って "first" という名前の最初のコンテナを起動してみましょう。 - lxc launch ubuntu first + + LXD はデフォルトでイメージサーバが 3 つ登録されています: + + ubuntu: (Ubuntu stable イメージ用 ) + ubuntu-daily: (Ubuntu daily イメージ用 ) + images: (その他多数のディストリビューション用 ) + + + + + stable の Ubuntu イメージは以下のようにリスト表示できます: + lxc image list ubuntu: | less + + + + "first" という名前の最初のコンテナを起動するには、以下のようにします: + lxc launch ubuntu:14.04 first @@ -396,9 +410,9 @@ LXC 開発元はこのようなサーバを https://images.linuxcontainers.org;>https://images.linuxcontainers.org で運用しています。ここでは、色々な Linux ディストリビューションのイメージを自動的に作成して提供しています。 - - このイメージサーバに接続するには、以下のように実行します。 - lxc remote add images images.linuxcontainers.org + + このサーバはデフォルトで LXD に登録されています。もしこのサーバを使わない場合は、デフォルトの登録を変更したり、削除したりできます。 ___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
[lxc-devel] [lxc/lxc] 79dff3: doc: add copy hook explanation to Japanese lxc-cop...
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: 79dff39e8994fc697884fed4f27613b9093058f4 https://github.com/lxc/lxc/commit/79dff39e8994fc697884fed4f27613b9093058f4 Author: KATOH YasufumiDate: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M doc/ja/lxc-copy.sgml.in Log Message: --- doc: add copy hook explanation to Japanese lxc-copy(1) Update for commit cc0607a Signed-off-by: KATOH Yasufumi Commit: 352470062e49751bca512a2817446962a35aedc0 https://github.com/lxc/lxc/commit/352470062e49751bca512a2817446962a35aedc0 Author: KATOH Yasufumi Date: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M doc/ja/lxc-attach.sgml.in Log Message: --- doc: improve Japanese lxc-attach(1) Explain that the pipe symbol needs to be escaped for -e and -s. Update for commit 759d521 Signed-off-by: KATOH Yasufumi Commit: 130dae08d6d30614b74e4f20a97ed5f2456da423 https://github.com/lxc/lxc/commit/130dae08d6d30614b74e4f20a97ed5f2456da423 Author: Christian Brauner Date: 2016-03-03 (Thu, 03 Mar 2016) Changed paths: M doc/ja/lxc-attach.sgml.in M doc/ja/lxc-copy.sgml.in Log Message: --- Merge pull request #866 from tenforward/japanese_man Update Japanese lxc-attach(1) and lxc-copy(1) Compare: https://github.com/lxc/lxc/compare/dfc7616801e3...130dae08d6d3___ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel