Re: [lxc-users] Clarification

2018-05-27 Thread Andrey Repin 
Greetings, Thouraya TH!

>  containers share the same operating system as the host.

That's not quite correct.
Containers share the host //kernel//. The definition of "OS" is a bit blurry
in this regard.
Let's just say, you can run different set of utilities (what is usually
defined as "distribution") as long as they can be run on the same kernel.

> so i cnanot do  lxc-create -n c1 -o windows on ubuntu system ? that's it ?
> i can create windows container only on windows system using docker for 
> example ?

I'm not sure, how exactly Docker does that, if at all, so can't comment.


-- 
With best regards,
Andrey Repin
Sunday, May 27, 2018 21:14:38

Sorry for my terrible english...
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Clarification

2018-05-26 Thread Sean McNamara 
That's correct. LXC and LXD are not a hypervisor; the container runs
user-space code on the same kernel as the host kernel. Windows has its
own separate kernel and its userspace is incapable of running on the
Linux kernel for many reasons (different executable format, different
kernel ABI/API, different responsibilities for userspace vs. kernel,
etc.)

*Some* Windows programs can be emulated with limited success using
Wine, but Wine will probably never support 100% of all Windows
programs at full functionality. If you wanted to run a specific
Windows-only program that happened to be supported by Wine in an LXC
or LXD container, you could do that by installing a Linux distribution
in a container, and running the program under wine in the container.
That would probably work, but your results would depend on how well
Wine supports the program you need to run.

If you really want to just run *Windows itself* rather than emulating
certain programs, the only way to do that on top of Linux is to use a
proper hypervisor, like KVM, VMware, or VirtualBox. They will emulate
physical *hardware* and run the real Windows kernel on top of your
base operating system -- with a performance cost, of course.



On Sat, May 26, 2018 at 6:51 PM, Thouraya TH  wrote:
> Hi all,
> containers share the same operating system as the host.
> so i cnanot do  lxc-create -n c1 -o windows on ubuntu system ? that's it ?
> i can create windows container only on windows system using docker for
> example ?
> Thank you so much for answer.
> Kind regards.
>
>
>
> ___
> 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] clarification

2016-08-15 Thread Matt Barrett 
Interesting. I've been using LXD but I thought of it as LXD for the
container server side which hosted LXC containers. I guess that was the
wrong way of looking at it based on your comments.

On Aug 11, 2016 5:24 PM, "Sean McNamara"  wrote:

> On Thu, Aug 11, 2016 at 8:12 PM, Worth Spending 
> wrote:
> > I'm currently reading thru the documentation at:
> https://linuxcontainers.org
> > to learn lxc.
> >
> > There seems to be multiple ways of running lxc commands.
> >
> > lxc-start, lxc-stop, lxc-attach, lxc-ls
>
>
> The "hyphenated" commands are from the "legacy" LXC command line interface.
>
>
> >
> > or lxc with sub commands.
> >
> > lxc start
> >
> > lxc stop
> >
> > lxc list
>
> The "non-hyphenated" commands are for the **LXD** (D, not C) container
> hypervisor. This is a completely different product/application than
> LXC. The LXD client binary, `lxc`, is extremely unfortunately named
> and thus very confusing for new users, which has been discussed about
> 9000 times on this mailing list.
>
>
>
>
> >
> > So, the question is: What is the current preferred usage for lxc
> commands?
> > hyphenated commands or lxc with sub commands?
>
>
> You need to look into the benefits and drawbacks of using either LXC
> or LXD (consider each one separately in terms of what it offers, how
> it's implemented, and how it's used) and make a decision. If you use
> the hyphenated LXC commands, any containers you create in that
> environment will be completely invisible to LXD, and vice versa. They
> each keep track of containers differently so LXD does not know about
> LXC containers and LXC does not know about LXD containers.
>
>
> >
> > Thanks...
> >
> > ___
> > 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
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] clarification

2016-08-11 Thread Worth Spending 
I thought this was the case as I assumed "lxc-" commands were legacy.  
All I was looking for was a conformation.  Sorry I asked.



On 08/11/2016 07:24 PM, Sean McNamara wrote:

On Thu, Aug 11, 2016 at 8:12 PM, Worth Spending  wrote:

I'm currently reading thru the documentation at: https://linuxcontainers.org
to learn lxc.

There seems to be multiple ways of running lxc commands.

lxc-start, lxc-stop, lxc-attach, lxc-ls


The "hyphenated" commands are from the "legacy" LXC command line interface.



or lxc with sub commands.

lxc start

lxc stop

lxc list

The "non-hyphenated" commands are for the **LXD** (D, not C) container
hypervisor. This is a completely different product/application than
LXC. The LXD client binary, `lxc`, is extremely unfortunately named
and thus very confusing for new users, which has been discussed about
9000 times on this mailing list.





So, the question is: What is the current preferred usage for lxc commands?
hyphenated commands or lxc with sub commands?


You need to look into the benefits and drawbacks of using either LXC
or LXD (consider each one separately in terms of what it offers, how
it's implemented, and how it's used) and make a decision. If you use
the hyphenated LXC commands, any containers you create in that
environment will be completely invisible to LXD, and vice versa. They
each keep track of containers differently so LXD does not know about
LXC containers and LXC does not know about LXD containers.



Thanks...

___
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


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

Re: [lxc-users] clarification

2016-08-11 Thread Sean McNamara 
On Thu, Aug 11, 2016 at 8:12 PM, Worth Spending  wrote:
> I'm currently reading thru the documentation at: https://linuxcontainers.org
> to learn lxc.
>
> There seems to be multiple ways of running lxc commands.
>
> lxc-start, lxc-stop, lxc-attach, lxc-ls


The "hyphenated" commands are from the "legacy" LXC command line interface.


>
> or lxc with sub commands.
>
> lxc start
>
> lxc stop
>
> lxc list

The "non-hyphenated" commands are for the **LXD** (D, not C) container
hypervisor. This is a completely different product/application than
LXC. The LXD client binary, `lxc`, is extremely unfortunately named
and thus very confusing for new users, which has been discussed about
9000 times on this mailing list.




>
> So, the question is: What is the current preferred usage for lxc commands?
> hyphenated commands or lxc with sub commands?


You need to look into the benefits and drawbacks of using either LXC
or LXD (consider each one separately in terms of what it offers, how
it's implemented, and how it's used) and make a decision. If you use
the hyphenated LXC commands, any containers you create in that
environment will be completely invisible to LXD, and vice versa. They
each keep track of containers differently so LXD does not know about
LXC containers and LXC does not know about LXD containers.


>
> Thanks...
>
> ___
> 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

[lxc-users] clarification

2016-08-11 Thread Worth Spending 
I'm currently reading thru the documentation at: 
https://linuxcontainers.org to learn lxc.


There seems to be multiple ways of running lxc commands.

lxc-start, lxc-stop, lxc-attach, lxc-ls

or lxc with sub commands.

lxc start

lxc stop

lxc list

So, the question is: What is the current preferred usage for lxc 
commands?  hyphenated commands or lxc with sub commands?


Thanks...

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