-
Notifications
You must be signed in to change notification settings - Fork 373
Pod information is left while assigning host networking with docker #652
Comments
yay for the soak test! 😄 Do you see the same behaviour using the latest runtime commit? FTR, I don't but I'm using latest everything. |
/cc @grahamwhaley. |
@GabyCT Yeah same question as @jodh-intel, are you seeing the issue with the latest commit? |
@amshinde and @jodh-intel , well I ran the
And the issue is still there
|
Hi @GabyCT - can you list the versions of proxy, shim and image/agent you are running too? Just paste in the output of |
@jodh-intel , here it is the information
|
it looks like the agent information was not generated, however, here it is
|
You need to run To save us time, please could you explain if you're using the packaged version of everything or you've built all the components, or a combination of both? |
from what I can see the only thing that is not updated to latest is the agent, let me update it and test again |
what sort of graph driver (storage) do you have on your docker - and what is your docker version. I have to wonder if the graph driver might make a difference to such things - we have quite different mounts and accesses which maybe prevent something being free'd up for instance. |
@grahamwhaley here it is the info
|
Well, I updated the latest agent
and no luck. Here it is all the info of
Runtime config filesRuntime default config files
Runtime config file contentsConfig file
Image details
Initrd detailsNo initrd LogfilesRuntime logsRecent runtime problems found in system journal:
Proxy logsRecent proxy problems found in system journal:
Shim logsRecent shim problems found in system journal:
Container manager detailsHave DockerOutput of "
Output of "
Output of "
Have KubernetesOutput of "
Output of "
Output of "
Have
Output of "
PackagesHave
Have
|
Hi @GabyCT - the output above is showing that you are using an osbuilder image based on Clr with agent version |
Closing this issue as is not longer present with the following configuration
|
not all the hypervisors connect a socket to /dev/console, so it's no possible to get the agent's logs from a unix socket. This patch is to connect the logger (logrus) to a vsock port, this way the logs can be read in the host using vsocks or hybrid vsocks. fixes kata-containers#652 Signed-off-by: Julio Montes <[email protected]>
While performing
A file is left at
And that is causing that the execution of the soak test fails.
Using the following setup:
kata-runtime : 1.2.0
commit : f70d6d2
OCI specs: 1.0.1
kata-agent version 1.2.0-4c723f49d590813c311dcd0e2aab19616d757f19
kata-proxy version 1.2.0-6f209b7f3c586c5f17b52df8bd5d6edbc45ee477
kata-shim version 1.2.0-0a37760c0224167143cb3cc920c78f5147f52e70
The text was updated successfully, but these errors were encountered: