Skip to content

[agent] improve log level/message on expected failures and avoid misleading logs #99

@bcho

Description

@bcho

Logs like this are misleading as docker not found is expected state. We should not log it as error. We should indicate what is the goal state here.

2026-04-28T19:52:11Z [E]  Failed to stop docker.socket: Unit docker.socket not loaded.
2026-04-28T19:52:12Z [E]  Unit docker.socket does not exist, proceeding anyway.
2026-04-28T19:52:12Z [E]  Created symlink /etc/systemd/system/systemd-nspawn@.service.requires/nftables-flush.service → /etc/systemd/system/nftables-flush.service.
2026-04-28T19:52:12Z [E]  Created symlink /etc/systemd/system/docker.socket → /dev/null.

Similar patterns can be found for installing required system packages on the host.

2026-04-28T19:52:04Z [E]  dpkg-query: no packages found matching debootstrap

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions