[lxc-users] lxc file push garbling existing file

Wed Apr 6 20:54:13 UTC 2016

On Wed, Apr 06, 2016 at 03:51:12PM -0500, Craig Tataryn wrote:
> Really sorry to be a pain but I am confused...
> 
> I ran:
> 
> sudo apt-get install lxd
> sudo apt-get install lxc

That's because you forgot to update lxd-client which is the package
providing the "lxc" command.

> 
> When I run an `apt-cache policy` they both seem to be running the latest
> and greatest respective 2.0 rc versions.
> 
> However, when I run `sudo lxc --version` I still see 0.19, even though
> `sudo lxd --version` shows the rc8 as I expected.
> 
> Also, I run `sudo lxc list` and I get the error message:
> 
>      error: Response was missing `api_compat`
> 
> I did notice a big warning message that popped up when installing lxd, not
> sure if it's related?
> 
> http://imgur.com/a/kqV5N
> 
> Craig
> 
> 
> 
> On Wed, Apr 6, 2016 at 3:26 PM, Stéphane Graber <stgraber at ubuntu.com> wrote:
> 
> > Nope, no need to stop the containers.
> >
> > Old package versions may shut them all down before doing the upgrade but
> > that's not necessary at all and newer packages no longer do that.
> >
> > On Wed, Apr 06, 2016 at 03:22:34PM -0500, Craig Tataryn wrote:
> > > I forgot to ask. When upgrading LXD is there any need to stop the
> > > containers before doing so?
> > >
> > > Craig.
> > >
> > > On Wed, Apr 6, 2016 at 3:18 PM, Craig Tataryn <craiger at tataryn.net>
> > wrote:
> > >
> > > > Thanks for the background. My vote is to rename the LXD command-line
> > tools
> > > > project to: LXE ;)
> > > >
> > > > Craig.
> > > >
> > > > On Wed, Apr 6, 2016 at 2:28 PM, Stéphane Graber <stgraber at ubuntu.com>
> > > > wrote:
> > > >
> > > >> The lxc and lxd binaries come from LXD which is currently at rc8.
> > > >>
> > > >> The lxc-* binaries are for the "old" user experience which is LXC
> > > >> itself, that's what we just released as 2.0 earlier today.
> > > >>
> > > >>
> > > >> LXD changelog: https://linuxcontainers.org/lxd/news/
> > > >> LXC changelog: https://linuxcontainers.org/lxc/news/
> > > >>
> > > >> Yes, the naming of the "lxc" command is very confusing, we are well
> > aware.
> > > >>
> > > >> On Wed, Apr 06, 2016 at 02:25:11PM -0500, Craig Tataryn wrote:
> > > >> > I just saw that 2.0 was released! Congrats! You guys have quick
> > release
> > > >> > cycles, I don't consider 6 months that long ago!
> > > >> >
> > > >> > Q1. Just out of curiosity how does the version displayed using the
> > > >> >  '--version' switch coincide with the releases on the news page? [1]
> > > >> >
> > > >> > Also, I find this very interesting... prior to running `apt-get
> > update`
> > > >> I
> > > >> > did an `apt-cache policy lxd` and I saw:
> > > >> >
> > > >> > Candidate: 2.0.0~rc15-0~ubuntu14.04.1~ppa1
> > > >> >
> > > >> > Then I ran `apt-get update` followed by `apt-cache policy lxd` and
> > I now
> > > >> > see:
> > > >> >
> > > >> > Candidate: 2.0.0~rc8-0~ubuntu5~ubuntu14.04.1~ppa1
> > > >> >
> > > >> > Q2. rc15 > rc8 no? Why would that be?
> > > >> >
> > > >> > P.S. I love this project and I'm by no means a DevOps but I've
> > managed
> > > >> to
> > > >> > build myself a sweet Build/Deploy System and a Server container for
> > my
> > > >> app
> > > >> > all by using LXD on a cheap VPS. I struggled with Docker for a day,
> > then
> > > >> > found this post [2], and never looked back.
> > > >> >
> > > >> > Craig.
> > > >> >
> > > >> > [1] - https://linuxcontainers.org/lxc/news/
> > > >> > [2] - https://www.flockport.com/lxc-vs-docker/
> > > >> >
> > > >> > On Wed, Apr 6, 2016 at 10:09 AM, Stéphane Graber <
> > stgraber at ubuntu.com>
> > > >> > wrote:
> > > >> >
> > > >> > > On Wed, Apr 06, 2016 at 09:55:08AM -0500, Craig Tataryn wrote:
> > > >> > > > I've setup an automated deploy script that does the following:
> > > >> > > >
> > > >> > > > * Uploads (via scp) a file to a host
> > > >> > > > * Executes (via ssh) the `lxc file push` command to a container
> > on
> > > >> that
> > > >> > > host
> > > >> > > >
> > > >> > > > Every once in a while the file that is pushed to the container
> > > >> winds up
> > > >> > > > being garbled somehow.  I've experienced this for both text and
> > > >> binary
> > > >> > > > files.  When I crack open the text file typically it appears
> > that
> > > >> the
> > > >> > > last
> > > >> > > > line of the file duplicates some partial remnants of the
> > previous
> > > >> file
> > > >> > > that
> > > >> > > > was overwritten.
> > > >> > > >
> > > >> > > > My current work around is to issue an `lxc exec -- rm -f
> > <existing
> > > >> file>`
> > > >> > > > before doing the push.
> > > >> > > >
> > > >> > > > Before I go through a lot of trial-and-error I was wondering if
> > > >> anyone
> > > >> > > > knows if this is a known issue, or have otherwise experienced
> > this
> > > >> for
> > > >> > > > themselves?
> > > >> > > >
> > > >> > > > Versions:
> > > >> > > > LXC: 0.19
> > > >> > > > LXD: 0.19
> > > >> > > > LXCFS: 0.10
> > > >> > >
> > > >> > > Please upgrade to something a bit more recent, that's all been
> > fixed
> > > >> > > months ago :)
> > > >> > >
> > > >> > > 0.19 is from September 2015, we are now at 2.0.0 rc8.
> > > >> > >
> > > >> > > >
> > > >> > > > Thanks,
> > > >> > > >
> > > >> > > > Craig.
> > > >> > >
> > > >> > > > _______________________________________________
> > > >> > > > lxc-users mailing list
> > > >> > > > lxc-users at lists.linuxcontainers.org
> > > >> > > > http://lists.linuxcontainers.org/listinfo/lxc-users
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Stéphane Graber
> > > >> > > Ubuntu developer
> > > >> > > http://www.ubuntu.com
> > > >> > >
> > > >> > > _______________________________________________
> > > >> > > lxc-users mailing list
> > > >> > > lxc-users at lists.linuxcontainers.org
> > > >> > > http://lists.linuxcontainers.org/listinfo/lxc-users
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Craig Tataryn
> > > >> > blog: http://tataryn.net
> > > >> > podcast: http://www.basementcoders.com/
> > > >> > irc: ThaDon on freenode #basementcoders
> > > >> > twitter: @craiger
> > > >>
> > > >> > _______________________________________________
> > > >> > lxc-users mailing list
> > > >> > lxc-users at lists.linuxcontainers.org
> > > >> > http://lists.linuxcontainers.org/listinfo/lxc-users
> > > >>
> > > >>
> > > >> --
> > > >> Stéphane Graber
> > > >> Ubuntu developer
> > > >> http://www.ubuntu.com
> > > >>
> > > >> _______________________________________________
> > > >> lxc-users mailing list
> > > >> lxc-users at lists.linuxcontainers.org
> > > >> http://lists.linuxcontainers.org/listinfo/lxc-users
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Craig Tataryn
> > > > blog: http://tataryn.net
> > > > podcast: http://www.basementcoders.com/
> > > > irc: ThaDon on freenode #basementcoders
> > > > twitter: @craiger
> > > >
> > >
> > >
> > >
> > > --
> > > Craig Tataryn
> > > blog: http://tataryn.net
> > > podcast: http://www.basementcoders.com/
> > > irc: ThaDon on freenode #basementcoders
> > > twitter: @craiger
> >
> > > _______________________________________________
> > > lxc-users mailing list
> > > lxc-users at lists.linuxcontainers.org
> > > http://lists.linuxcontainers.org/listinfo/lxc-users
> >
> >
> > --
> > Stéphane Graber
> > Ubuntu developer
> > http://www.ubuntu.com
> >
> > _______________________________________________
> > lxc-users mailing list
> > lxc-users at lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
> >
> 
> 
> 
> -- 
> Craig Tataryn
> blog: http://tataryn.net
> podcast: http://www.basementcoders.com/
> irc: ThaDon on freenode #basementcoders
> twitter: @craiger

> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20160406/a22628d2/attachment.sig>