Linux Container Development
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: lxc-console on Debian Squeeze - both 0.7.2 and 0.7.5 less than happy
Date: Wed, 4 Jan 2012 14:38:52 -0500	[thread overview]
Message-ID: <20120104193852.GA22727@black.transpect.com> (raw)

Hi,

On a Debian Squeeze system I'm trying to run some Debian Squeeze containers.
I've been having trouble with lxc-console. Sometimes it connects fine. Other
times it doesn't. This is with the Squeeze version of LXC, unfortunately
only 0.7.2. So I wanted to see if 0.7.5 would be better. Installed from tar
to its default location. Symlinked /usr/local/var/lib/lxc to /var/lib/lxc
where I already had a couple of containers configured.

That's enough to get the containers to start from the 0.7.5 lxc-start. But
it leaves the 0.7.5 lxc-console totally unhappy. It's obviously looking at
things differently than lxc-start and lxc-info:

# lxc-info -n xfer
state:   RUNNING
pid:      1414

# lxc-console -n xfer
lxc-console: 'xfer' is stopped

The 'xfer' container is running, and can be connected to by SSH just fine.
But I'd like to get lxc-console working dependably. Again, with 0.7.2
(providing that the 0.7.2 lxc-start was used) it connects or fails to
seemingly randomly. It's an older version. Who cares? But how do I convince
the 0.7.5 version that what lxc-info can see, it should see too, and connect
with?

Thanks,
Whit

                 reply	other threads:[~2012-01-04 19:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120104193852.GA22727@black.transpect.com \
    --to=whit-m6g8sdwvnhfby3ivrkzq2a@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox