logging: journald on a container runs it with the journal as its log driver and names the place in the spec, so moving it recreates the container; any place other than the journal is refused. This is what lets a jail read a container's service by its name (hq ADR 0179, to-be 31). Rolls first: an older host refuses a declaration carrying the field.
Tests: declaration parse/refuse, run arguments and spec in internal/apply/logging_test.go.
`logging: journald` on a container runs it with the journal as its log driver and names the place in the spec, so moving it recreates the container; any place other than the journal is refused. This is what lets a jail read a container's service by its name (hq ADR 0179, to-be 31). Rolls first: an older host refuses a declaration carrying the field.
Tests: declaration parse/refuse, run arguments and spec in `internal/apply/logging_test.go`.
A jail reads a log; a container's output went to a file of the runtime's own under a path that
changes on recreate, so no jail could read a container's service. logging: journald runs the
container with the journal as its driver, named in the spec so moving it recreates it; any other
place is refused.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
logging: journaldon a container runs it with the journal as its log driver and names the place in the spec, so moving it recreates the container; any place other than the journal is refused. This is what lets a jail read a container's service by its name (hq ADR 0179, to-be 31). Rolls first: an older host refuses a declaration carrying the field.Tests: declaration parse/refuse, run arguments and spec in
internal/apply/logging_test.go.