Comments (8)
What exactly does this mean?
from lxd.
On Wed, Dec 09, 2015 at 02:26:09PM -0800, Sven R. Kunze wrote:
What exactly does this mean?
we don't capture stdout/stderr by default since they could be very
large and the user may never request them. the idea with this flag is
for users to be able to capture them to be stored for later
acquisition.
I think we initially filed this when we kept operations around
forever. Now that we delete them, it may not even make sense to have
this; if you want to interact with the command, you should probably
just use interactive mode.
Reply to this email directly or view it on GitHub:
lxc/incus#180 (comment)
from lxd.
Yeah, if we wanted to still be able to retrieve them, we'd need to have an API under the operation to fetch them and then keep the operation in running state until after they've been fetched and the operation cancelled.
from lxd.
You mean something for nohup lxc exec test -- ping localhost > log 2>&1 &
but different?
from lxd.
On Wed, Dec 09, 2015 at 02:54:49PM -0800, Sven R. Kunze wrote:
You mean something for
nohup lxc exec test -- ping localhost > log 2>&1 &
but different?
i don't know what you mean by "but different" here, but yes. something
to capture the output from commands that are run in non-interactive
mode.
Reply to this email directly or view it on GitHub:
lxc/incus#180 (comment)
from lxd.
This bug is about the LXD API rather than the client.
There is a feature in our API which the client doesn't expose that allows you to spawn a command inside the container and not attach to it, in that mode, the command will just run to completion and the background operation will return.
It's in that mode that we've been considering adding a way to keep the operation around and expose the content of stdout and stderr as it was when the command completed.
from lxd.
There is a feature in our API which the client doesn't expose that allows you to spawn a command inside the container and not attach to it, in that mode, the command will just run to completion and the background operation will return.
I didn't know that.
However, it sounds extremely useful for automation and to get rid of that weird shell-specific file redirection syntax. (I daresay built-in logrotate-like functionality would be great here, too. ;) )
Te me, non-interactive stdout and stderr are basically log data only. So, you basically want something like a tee
cmd to peek into the current stream of log data, right?
from lxd.
Going to take a stab at this. One of my concerns when first thinking through this was polluting the host with all that console output. Luckily, we've since grown a log expiry mechanism that we can use for this.
Current plan is:
- Redirect stdout and stderr (independently) to two temp files inside the log directory of the container
- In the operation metadata, include the relative URLs to those log files
That will then allow the client to retrieve stdout and stderr for the next 48 hours, after which, the log expiry mechanism will kick in and clear those files.
from lxd.
Related Issues (20)
- Etag check is missing for storage bucket update handler
- Networks of type physical managed do not expose state HOT 2
- Can't start containers / zpool didn't mount HOT 2
- Unused flags when adding TPM to VMs HOT 2
- port 53 forwarding kept giving internal dns names HOT 1
- Restricted users loading all operations causing 500
- Apparmor DENIED for name="/sys/devices/system/node/" and comm="qemu-img" HOT 13
- image source image_type is empty string HOT 3
- `security.devlxd.images` regressed somewhere after `5.0` HOT 2
- Potential duplicate QEMU device ID when using long device names HOT 3
- doc: Incorrect unit for limits.memory
- LXD is missing support for `binfmt_misc` namespace HOT 1
- storage pool create failure due to ext4's lost+found directory HOT 2
- Enable `security.nesting` by default for unprivileged containers and modern enough images HOT 2
- `PATCH /1.0/projects/<project>` removes existing configuration HOT 1
- Images failing to build for a long time get evicted from `images:` HOT 7
- openEuler images are not published
- Unable to start instances on zfs backed LXD if the pool reports as DEGRADED HOT 2
- lxd-imagebuilder GPG tests should be updated
- Auth: OIDC login flow fails in an LXD cluster if different members handle different stages of the flow HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lxd.