You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request that all our containers list via eve list
~# eve list
CONTAINER IMAGE RUNTIME
debug - io.containerd.runc.v2
edgeview - io.containerd.runc.v2
guacd - io.containerd.runc.v2
newlogd - io.containerd.runc.v2
pillar - io.containerd.runc.v2
vtpm - io.containerd.runc.v2
watchdog - io.containerd.runc.v2
wlan - io.containerd.runc.v2
wwan - io.containerd.runc.v2
xen-tools - io.containerd.runc.v2
show the name when connected to them.
So far only pillar and newlogd show a reference in the prompt:
~# eve enter newlogd
/newlog #
~# eve enter pillar
(ns: pillar) :/#
For the rest of the containers we only see a change from ‘~#’ → '/#' .
It would be really appreciated for debug container as we often instruct customer from CS side to ensure Customer is actually in the debug container before issuing a specific command but might come in handy at some point in the future with the other containers too. I personally would opt for how it is done with pillar container prompt.
The text was updated successfully, but these errors were encountered:
I would like to request that all our containers list via eve list
~# eve list
CONTAINER IMAGE RUNTIME
debug - io.containerd.runc.v2
edgeview - io.containerd.runc.v2
guacd - io.containerd.runc.v2
newlogd - io.containerd.runc.v2
pillar - io.containerd.runc.v2
vtpm - io.containerd.runc.v2
watchdog - io.containerd.runc.v2
wlan - io.containerd.runc.v2
wwan - io.containerd.runc.v2
xen-tools - io.containerd.runc.v2
show the name when connected to them.
So far only pillar and newlogd show a reference in the prompt:
~# eve enter newlogd
/newlog #
~# eve enter pillar
(ns: pillar) :/#
For the rest of the containers we only see a change from ‘~#’ → '/#' .
It would be really appreciated for debug container as we often instruct customer from CS side to ensure Customer is actually in the debug container before issuing a specific command but might come in handy at some point in the future with the other containers too. I personally would opt for how it is done with pillar container prompt.
The text was updated successfully, but these errors were encountered: