We've been using this in development versions of FCOS for some time, and it's been working well (or at least, it errors out for now the way we expect it to).
@jlebon, I think what might be happening is, if you are using
login is the mechanism displaying the MOTD.
login will only look for
/etc/motd by default, or a specified list of paths with
Have been meaning to add the
/etc/motd.d/console-login-helper-messages.motd path with this: https://github.com/coreos/coreos-assembler/issues/244 (though this only solves it for
console-login-helper-messages is relying on something to search
/etc/motd.d and follow the symlink from
/run/console-login-helper-messages/console-login-helper-messages.motd - sshd does this today. The generated MOTD should display after the steps you followed, if logging in using SSH.
Will make a note in the docs of the config required for
login vs. it showing through
sshd by default.
Hmm, so when I do:
# echo "hello" > /run/console-login-helper-messages/motd.d/00_hello # systemctl restart console-login-helper-messages-motdgen.service # cat /run/console-login-helper-messages/console-login-helper-messages.motd Fedora (29 (Cloud Edition)) hello
And then log out and back in, I don't see the motd. I'm testing this on FCOS, which also has an
/etc/motd, and logging back in just shows that MOTD instead, though I did try to delete
/etc/motd to see if it would generate a new one. When does this show up exactly?