Re: [lxc-users] Looking for LXD Container with AWS CDN Experience?
On 2019-03-18 01:09, Ray Jender wrote: If there is anyone experienced with using the Amazon Cloudfront with an LXD container, I could really use a little help! Wat are you trying to achieve? LXD with Amazon CloudFront isn't really used differently than a standalone or a fully virtual system like KVM or Xen. Tomasz Chmielewski https://lxadm.com ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] LXD for OpenWrt
Hello Florian, Florian Eckert writes: > Hello Free, > > I'm working on packaging lxd for OpenWrt. Great! I've been an OpenWrt user and still have a LinkSys wireless router with it on, although I don't use it anymore these days. > I started a pullrequest discussion and a also added a first proof of > concept makefile. > https://github.com/openwrt/packages/pull/8466 > > Apart from the fact that I have to package lxd with the toolchain for go > at OpenWrt, I have to compile dqlite and sqlite first. > > 1. A new dqlite library. With dqlite I don't see a problem for now to > get this packaged in OpenWrt. > > 2. A patched sqlite version from you/CanonicalLtd > > This results in the following questions to you > > 1. Because the sqlite library is a patched version I think I can not use > the already included OpenWrt version? > https://github.com/openwrt/packages/blob/master/libs/sqlite3/Makefile Correct. You can't use vanilla upstream SQLite. However, you can use that Makefile and possibly even the source tree if you wish, provided that: - You apply the patch needed by dqlite - You add --enable-replication to ./configure flags The patch with respect to the latest SQLite version is published here: https://github.com/CanonicalLtd/sqlite/releases/latest it's currently sqlite-3.27.2.diff is regularly updated once new SQLite versions come out. > 2. Why do you not merge your changes upstream? In the medium term, I do plan to submit the changes upstream. However SQLite developers are unbelievably conservatives when it comes to merging code from external contributors: "SQLite is not open-contribution. The project does not accept patches. Only 27 individuals have ever contributed any code to SQLite, and of those only 16 still have traces in the latest release. Only 3 developers have contributed non-comment changes within the previous five years and 96.4% of the latest release code was written by just two people. (The statistics in this paragraph were gathered on 2018-02-05.)" So I'll wait until I'm absolutely certain that the patch won't need any further modification, which is not the case right now. > 3. Why does the master branch from your repositry follows the sqlite > upstream version? Because it's a patch, not a fork, so we regularly pull from upstream. > It confuses me that the History is disorderd and so I do not know > what the changes you made are SQLite uses a VCS called "fossil" wrote by its main author. There are third parties providing automatic export to git of the official fossil repository. The export used to work quite well, and I could use git workflows like merge to keep the history clean. However, since a couple of releases something was messed up, either upstream or by the conversion tool, and the head of the git mirror was not anymore a descendant of the latest release. So in order to avoid having to force a push, I had to change strategy and essentially commit diffs by hand. I don't think there's any way to avoid this, given that we don't want to force push. For packages, I recommend to forget about git, and always rely on the .diff artifact, which you can version control yourself if you wish > 4. Is this a fork? No, it's patch. > 3. What patches do I need on top of sqlite for lxd? Just the .diff published above. >If so does this influence the sqlite so that other software who uses > this do not work anymore or have a runtime problem? No, the patch adds behavior which is only triggered if you use certain new APIs. There is zero semantic changes for other software. Cheers, Free ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Looking for LXD Container with AWS CDN Experience?
If there is anyone experienced with using the Amazon Cloudfront with an LXD container, I could really use a little help! Please let me know. Ray ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] LXD for OpenWrt
Hello Free, I'm working on packaging lxd for OpenWrt. I started a pullrequest discussion and a also added a first proof of concept makefile. https://github.com/openwrt/packages/pull/8466 Apart from the fact that I have to package lxd with the toolchain for go at OpenWrt, I have to compile dqlite and sqlite first. 1. A new dqlite library. With dqlite I don't see a problem for now to get this packaged in OpenWrt. 2. A patched sqlite version from you/CanonicalLtd This results in the following questions to you 1. Because the sqlite library is a patched version I think I can not use the already included OpenWrt version? https://github.com/openwrt/packages/blob/master/libs/sqlite3/Makefile 2. Why do you not merge your changes upstream? 3. Why does the master branch from your repositry follows the sqlite upstream version? It confuses me that the History is disorderd and so I do not know what the changes you made are 4. Is this a fork? 3. What patches do I need on top of sqlite for lxd? If so does this influence the sqlite so that other software who uses this do not work anymore or have a runtime problem? Thanks for help and feedback Regards Florian ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] docker in LXD from snap?
On 2019-03-14 19:05, Sergiusz Pawlowicz wrote: On Thu, 14 Mar 2019 at 16:55, Tomasz Chmielewski wrote: Is the following guide also relevant for running docker in LXD installed from snap? https://stgraber.org/2016/04/13/lxd-2-0-docker-in-lxd-712/ yes, I am using docker - but container must be privileged for docker to run properly. I've just started a bionic container which is not privileged, and simple docker images seem to run fine. I did use this option though: security.nesting: "true" Tomasz Chmielewski https://lxadm.com ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] future of lxc/lxd? snap?
Hello have you read this documentation ? https://docs.snapcraft.io/installing-snap-on-centos/10020 26 février 2019 09:28 "Harald Dunkel" a écrit: > On 2/25/19 11:20 AM, Stéphane Graber wrote: >> snapd + LXD work fine on CentOS 7, it's even in our CI environment, so >> presumably the same steps should work on RHEL 7. >> > Apparently it doesn't work that fine: > > [root@centos7 ~]# yum install snapd > Loaded plugins: fastestmirror, langpacks > Loading mirror speeds from cached hostfile > * base: ftp.halifax.rwth-aachen.de > * extras: ftp.halifax.rwth-aachen.de > * updates: mirror.infonline.de > No package snapd available. > Error: Nothing to do > > Of course I found some howtos on the net (e.g. > https://computingforgeeks.com/install-snapd-snap-applications-centos-7), > but thats not the point. The point is to integrate LXD without 3rd-party > tools that are difficult to find and install on their own. > > Surely I don't blame you for the not-invented-here approach of others, but > LXD appears to be difficult to build or integrate, even on native Debian. > > Regards > Harri > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] lxc container rootfs dev folder permission are changing from ro to rw inside container
On 2019-02-25 17:27, Yasoda Padala wrote: Actual results: dev folder of container rootfs is read-only on host machine but inside container, it is writable. Please help with inputs on why the dev folder permissions are changed on lxc-attach. Can you paste the output of: mount cat /proc/mounts from the container? Tomasz Chmielewski https://lxadm.com ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
