Re: [lxc-users] LXD project status

2018-03-29 Thread gunnar.wagner 


so the 'snap-only' policy I thought would be applied for LXD is not that 
strict then and traditional .deb packages still exist?


On 3/29/2018 8:44 PM, Simos Xenitellis wrote:

On Thu, Mar 29, 2018 at 4:32 AM, gunnar.wagner
 wrote:


On 3/28/2018 2:45 AM, Michel Jansens wrote:

Does this means LXD 3.0 will be part of Ubuntu 18.04 next month?

I guess (as LXD is using snap packages by default, right) it's not a matter
of distribution any lomnger but more of distribution able to run snap
packages well (which not every distribution does as far as I know [i.e.
OpenSUSE])


Ubuntu 18.04 LTS will be based on LXD 3.0.xx, supported until 2018+5y = 2023.
Those that have the LXD snap ('lxd', stable channel), are likely to
get upgraded to 3.1, 3.2 and so on,
as the new versions appear.
It was mentioned on the forum in December that Ubuntu 18.04 LTS will
have by default the .deb version of LXD 3.0.

This happened with Ubuntu 16.04 LTS, which has LXD 2.0.xx (currently at 2.0.11)
and is supported until 2021. Ubuntu 16.04 LTS was launched with the
new LXD 2.0 at that time.

When you do 'snap info lxd', you get

...
channels:
   stable:2.21(5866) 49MB -
   candidate: 2.21(6005) 51MB -
   beta:  3.0.0.beta7 (6240) 55MB -
   edge:  git-9a60cd9 (6251) 55MB -
   2.0/stable:2.0.11  (5384) 21MB -
   2.0/candidate: 2.0.11  (5384) 21MB -
   2.0/beta:  ↑
   2.0/edge:  git-d71807e (6069) 20MB -

which means that there is the option to switch to the snap 'LTS'
version of LXD 2.0 ('2.0/stable').

Simos
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

---
This email has been checked for viruses by AVG.
http://www.avg.com


--
Gunnar Wagner | Yongfeng Village Group 12 #5, Pujiang Town, Minhang 
District, 201112 Shanghai, P.R. CHINA

mob +86.159.0094.1702 | skype: professorgunrad | wechat: 15900941702
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] LXD project status

2018-03-29 Thread Simos Xenitellis 
On Thu, Mar 29, 2018 at 4:32 AM, gunnar.wagner
 wrote:
>
>
> On 3/28/2018 2:45 AM, Michel Jansens wrote:
>>
>> Does this means LXD 3.0 will be part of Ubuntu 18.04 next month?
>
> I guess (as LXD is using snap packages by default, right) it's not a matter
> of distribution any lomnger but more of distribution able to run snap
> packages well (which not every distribution does as far as I know [i.e.
> OpenSUSE])
>

Ubuntu 18.04 LTS will be based on LXD 3.0.xx, supported until 2018+5y = 2023.
Those that have the LXD snap ('lxd', stable channel), are likely to
get upgraded to 3.1, 3.2 and so on,
as the new versions appear.
It was mentioned on the forum in December that Ubuntu 18.04 LTS will
have by default the .deb version of LXD 3.0.

This happened with Ubuntu 16.04 LTS, which has LXD 2.0.xx (currently at 2.0.11)
and is supported until 2021. Ubuntu 16.04 LTS was launched with the
new LXD 2.0 at that time.

When you do 'snap info lxd', you get

...
channels:
  stable:2.21(5866) 49MB -
  candidate: 2.21(6005) 51MB -
  beta:  3.0.0.beta7 (6240) 55MB -
  edge:  git-9a60cd9 (6251) 55MB -
  2.0/stable:2.0.11  (5384) 21MB -
  2.0/candidate: 2.0.11  (5384) 21MB -
  2.0/beta:  ↑
  2.0/edge:  git-d71807e (6069) 20MB -

which means that there is the option to switch to the snap 'LTS'
version of LXD 2.0 ('2.0/stable').

Simos
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Question regarding container affecting the system mounts

2018-03-29 Thread Avadhut Bhangui 
Sorry to respond to this email...
I have registered with lxc-users mailing list, but when i sent a query, i'm not 
sure its' reaching the whole distribution or not.
Can someone please help me with this?
/Avadhut. 

On Wednesday, 28 March, 2018, 11:06:58 PM IST, Ronak Desai 
 wrote:  
 
 Hi,

I came a cross a problem where if the containers are running then it
affects the unmount process of the system's mount points. I am not
using these mount points as shared partitions with container.

For example, I am using SD card and NAND as external storage device
and mounting it to a mount point in the ramfs. Then I am launching
containers and then when I try to unmount the NAND partition then my
"unmount" call succeeds but I don't see the UBIFS hooks being called
and because of that my UBI detach process fails. When I stopped the
container then I see that kernel is calling the unmount as I see my
debug prints inside the UBIFS for unmounting that partition. It seems
like the calls are buffered/queued because of container.

If I tried to mount my NAND partition once the container is up and try
to unmount then it does unmount and detach without issue. It seems
like there is an issue with namespace.

I am using 4.1.8 kernel . Please let me know if you need any
additional detail from my end.

Thanks in advance !

-- 
Ronak A Desai
Sr. Software Engineer
Airborne Information Solutions / RC Linux Platform Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ronak.de...@rockwellcollins.com
https://www.rockwellcollins.com/
___
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