Skip to content

ateom-gvisor: tag forwarded actor logs with ate.dev/container_name#290

Merged
Julian Gutierrez Oschmann (juli4n) merged 1 commit into
agent-substrate:mainfrom
BenTheElder:gvisor-container-name
Jun 23, 2026
Merged

ateom-gvisor: tag forwarded actor logs with ate.dev/container_name#290
Julian Gutierrez Oschmann (juli4n) merged 1 commit into
agent-substrate:mainfrom
BenTheElder:gvisor-container-name

Conversation

@BenTheElder

Copy link
Copy Markdown
Collaborator

While working on multi-container support for uVM in #287 I noticed how difficult it is to debug multi-container workloads.

This makes it a lot easier. TODO: We could support filtering on this in kubectl ate (cc Haven Xia (@HavenXia))

@BenTheElder Benjamin Elder (BenTheElder) marked this pull request as ready for review June 23, 2026 21:06
@BenTheElder

Copy link
Copy Markdown
Collaborator Author

NOTE: multi-container works fine on gVisor, and we have some demos with this. It's just all the container logs were impossible to distinguish previously.

Comment thread cmd/ateom-gvisor/internal/ateom/logger.go Outdated
Give each application container its own JSON log pipe (instead of multiplexing
every container onto one), and add a containerName argument to
WrapContainerLogs/StartJSONLogPipe that sets an ate.dev/container_name label.
Multi-container actors logs can now be demultiplexed by container.
@juli4n Julian Gutierrez Oschmann (juli4n) merged commit f5df01b into agent-substrate:main Jun 23, 2026
9 checks passed
@BenTheElder Benjamin Elder (BenTheElder) deleted the gvisor-container-name branch June 23, 2026 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants