New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

journalctl can't read lz4 compressed logs, e.g. from fedora nspawn containers #1988

Closed
euank opened this Issue Jun 3, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@euank
Contributor

euank commented Jun 3, 2017

Issue Report

Bug

Container Linux Version

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1353.8.0
VERSION_ID=1353.8.0
BUILD_ID=2017-05-30-2322
PRETTY_NAME="Container Linux by CoreOS 1353.8.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"

Expected Behavior

  1. journalctl can view the logs of a container launched with: systemd-nspawn --link-journal=host --boot

Actual Behavior

The logs cannot be viewed if the container has +LZ4 on its systemd.

Reproduction Steps

$ sudo machinectl pull-raw --verify=no https://dl.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-25-1.3.x86_64.qcow2
$ sudo systemd-run systemd-nspawn -M 'Fedora-Cloud-Base-25-1.3.x86_64' --link-journal=host --boot
$ sudo journalctl -M Fedora-Cloud-Base-25-1.3.x86_64
Journal file /var/log/journal/39947dff1f4e4099b1c1311715049f73/system@00055103080a1561-ed0009d903d5d686.journal~ uses an unsupported feature, ignoring file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment