Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.
This repository was archived by the owner on May 12, 2021. It is now read-only.

Remove kata-redirect-agent-output-to-journal.conf #484

@jodh-intel

Description

@jodh-intel

#415 added a systemd snippet to redirect agent output from the console to the journal in the guest.

This provides the right outcome when tracing with vsock enabled (since the journal logs are made available on the host thanks to script/vsock-to-text-server.sh. However, we do not want that behaviour for non vsock environments (in other words the default environment where a proxy is used).

The solution should be as simple as:

  • Delete kata-redirect-agent-output-to-journal.conf.
  • Update kata-agent.service.in to specify:
    StandardOutput=journal+console
    

However, I cannot get journal+console to work. A better approach however, is to have the agent handle this such that when vsock is enabled, it will redirect its own output to the journal (syslog). That obviously doesn't require systemd which means the behaviour would be correct when running the agent as init (PID 1).

Metadata

Metadata

Assignees

Labels

medium-priorityUrgent issue (resolve before unprioritised issues)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions