This looks very promising.. Do you have more examples as to how one can use ,,
specially the docker-compose way for multi-container approach?
-Yogesh
From: Ranjib Dey dey.ranjib at gmail.com
Date: Tue Oct 4 15:42:30 UTC 2016
Previous message:
On 2016-10-05 00:41, Tomasz Chmielewski wrote:
On 2016-10-05 00:05, Michael Peek wrote:
I could be completely wrong about everything, but here's what I think
is
going on:
If I'm correct then the version of cp you have inside the container
was
compiled without large file support enabled.
On 2016-10-05 00:13, Barve, Yogesh Damodar wrote:
For creating a docker container one can use dockerfile to specify all
the required software installation packages and initialization,
entrypoint directory and entrypoint command.
LXD or LXC virtualize the whole operating system, so some of
I have built something similar https://github.com/pagerduty/nut,
its bit buggy, and needs some more love (AST parser from docker & better
file copy, fuidshift logic).
I dont know if anything else is out there, but you can go pretty close by
just using `lxc-attach -n -- /bin/bash`and siphoning a
On 2016-10-05 00:05, Michael Peek wrote:
I could be completely wrong about everything, but here's what I think
is
going on:
If I'm correct then the version of cp you have inside the container was
compiled without large file support enabled. What constitutes a
"large"
file is dependent on
For creating a docker container one can use dockerfile to specify all the
required software installation packages and initialization, entrypoint
directory and entrypoint command.
What will be the equivalent in the LXC world? How can one specify
- the required packages for installations,
-
I'm getting a weird issue with cp used with "lxc exec container-name
/bin/bash /some/script.sh".
/some/script.sh launches /some/other/script.sh, which in turn may run
some other script.
One of them is copying data with cp.
In some cases, cp complains that "Value too large for defined data
