On Tue, Dec 8, 2015 at 3:07 PM, Eldon Kuzhyelil wrote:
> Hi
>
> Okay i am now doing doing it with ethernet.So basically i am trying to
> setup a webserver in my lxc container and my system is connected to router
> via ethernet cable.I want the web page to be visible from my
Hi
Okay i am now doing doing it with ethernet.So basically i am trying to
setup a webserver in my lxc container and my system is connected to router
via ethernet cable.I want the web page to be visible from my another system
connected to this LAN.What i have done right now is this
vi
Hi all,
2015-12-04 5:47 GMT-05:00 Eldon Kuzhyelil :
> Hi,
> I am using kubuntu 14.04 with lxc installed on it.I have created one lxc
> container and installed nginx webserver in that container and created a
> simple webpage displaying a welcome sentence.I am able to get this
On 08/12/15 18:07, Eldon Kuzhyelil wrote:
Okay i am now doing doing it with ethernet. So basically i am trying to
setup a webserver in my lxc container and my system is connected to router
via ethernet cable.I want the web page to be visible from my another system
connected to this LAN. What
Quoting Peter Steele (pwste...@gmail.com):
> On 12/07/2015 07:49 AM, Serge Hallyn wrote:
> >Quoting Peter Steele (pwste...@gmail.com):
> >>I'm actually not (yet) running lxcfs. My understanding was that it
> >>isn't absolutely required but it does offer several benefits. I'd
> >>planned to tackle
Quoting Van Dorsey (vandor...@client1st.com):
> My problem may be Ubuntu server related as I have not had time to
> try another O/S image yet.
>
> I had this environment working while using 15.04 and followed
> various setups blogs. I burned that all down and started over with
> 15.10.
>
>
Quoting david.an...@bli.uzh.ch (david.an...@bli.uzh.ch):
> But now happens something strange:
>
> When running 'lxc exec wily-with-upstart-1 /bin/bash' the prompt changes to
> root@wily-with-upstart-1 as expected, but then closes the shell in a few
> seconds, falling back on the host prompt.
>
On 12/08/2015 08:00 AM, Serge Hallyn wrote:
Ok, can you change the launch command in the scripts to
lxc-start -n $containername -L /tmp/$containername.cout -l trace -o
/tmp/$containername.dout -- /sbin/init log_target=console log_level=debug
The console output will go into the .cout file and
On 12/08/2015 02:21 PM, Peter Steele wrote:
In this case of course the containers are using the stock downloaded
CentOS 7 image instead of my custom image. I was unable to reproduce
the systemd error through multiple start/stop tests of my
containers. They always started up without any
Quoting Peter Steele (pwste...@gmail.com):
> On 12/08/2015 08:00 AM, Serge Hallyn wrote:
> >Ok, can you change the launch command in the scripts to
> >
> >lxc-start -n $containername -L /tmp/$containername.cout -l trace -o
> >/tmp/$containername.dout -- /sbin/init log_target=console
On 12/08/2015 11:10 AM, Peter Steele wrote:
On 12/08/2015 08:00 AM, Serge Hallyn wrote:
Ok, can you change the launch command in the scripts to
lxc-start -n $containername -L /tmp/$containername.cout -l trace -o
/tmp/$containername.dout -- /sbin/init log_target=console
log_level=debug
The
11 matches
Mail list logo