Open stuclem opened 7 years ago
@chengwang86 I just found this one and migrated it to the vic-product repo. Do we need this in the doc for 1.2? Thanks!
@stuclem Yes, I think we do need this for 1.2 since the corresponding feature (vic-machine configure --debug) is in 1.2
Awaiting confirmation from @chengwang86 as to whether this was implemented in 1.2.
@stuclem Here are the steps:
docker stop
govc
.govc vm.change -vm vmName -e guestinfo.vice./diagnostics/debug=Debug_level
. Here vmName
is usually containerName-containerShortID
and can be replaced by containerName*
. The user set the Debug_level
to a desired integer.docker start
.Looks like this slipped through the net.
Perhaps this would be more appropriate for a KB (or iKB) as there's no user-friendly container debug logging.
Moving this into the KB bucket.
@chengwang86 commented on Fri Apr 07 2017
User Statement:
As a VIC user, after I change the debug state of my VCH, new containers created by the VCH will take the updated debug state for logging. However, existing containers will still use the previous debug state. We need documentation on how to use
govc
or direct editing to update the debug state for such existing containers when needed.Acceptance Criteria: