update to buster

[aqw]

It would be great to have an updated image with Debian buster.

[teutat3s]

Just did a quick test with debian:latest and here's what happens when you try to install nginx

Setting up nginx (1.14.2-2+deb10u1) ...
Processing triggers for libc-bin (2.28-10) ...
Segmentation fault (core dumped)
Segmentation fault (core dumped)
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)

I believe lx-brand is not ready for buster yet, some syscalls are not available - see

TritonDataCenter/sdc-docker#136 (comment)

So it seems some internal library (or libraries) like libc are not working correctly - I would hazard a guess that it's due to a difference in the LX implementation for certain system call(s).

[aqw]

@teutat3s Ahh, thanks for the link. :-) I was not aware that they needed to add some missing syscalls to LX in order to support buster.

Promising though that OmniOS already has support. Hopefully the patch is to Joyent's liking.

[teutat3s]

Just a headsup: Tried a debian:latest which is buster via docker on triton.
Platform Image used is: 20200103T034110Z

libc-bin error seems to be gone as of first impression

I have to test more to see if other syscalls are still missing - but after a first look, looks like buster as lx-brand works now.

UPDATE: Creating a lx-brand debian buster image worked fine.
After startup, the first thing I noticed was that /var/log/syslog was missing. It seems that systemd in lx-brand needs a workaround for now:

Deactivate (comment) this line in systemd-logind and systemd-journald, eg. with
systemctl edit --full systemd-logind
systemctl edit --full systemd-journald

#NoNewPrivileges=yes

Then restart the services.

These are the error messages seen otherwise after first startup:

$ systemctl status systemd-logind
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-01-29 03:25:04 UTC; 8min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           https://www.freedesktop.org/wiki/Software/systemd/logind
           https://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 52194 (code=exited, status=227/NO_NEW_PRIVILEGES)

$ systemctl status systemd-journald
● systemd-journald.service - Journal Service
   Loaded: loaded (/etc/systemd/system/systemd-journald.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-01-29 03:13:59 UTC; 17min ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 22933 (code=exited, status=227/NO_NEW_PRIVILEGES)

[aqw]

I havn't tried it yet, but according to smartos-discuss, this buster LX image is working:

https://dsapid.root1.ass.de/ui/#!/configure/55bcd862-bb70-11e9-9991-7b9a40d4e95f

[stellarpower]

Know this issue was some time ago now and may be entirely irrelevant to the thread, but I just had an issue with XDG paths in my lx Focal zone under OmniOS (r151036), that could eventiually be traced back to systemd failures on boot that didn't show up, and the fix above seems to have sorted this. Might not be of any help, but, different host, different guest, lx branding was still affected.

[michaelkoetter]

FWIW, I started working on a Github pipeline for Debian 11 (bullseye). It produces the rootfs *.tar.gz which must then be fed into create-lx-image on a smartos instance (can't do this step on Github Actions yet).
As of now I can confirm the zone is booting and I can login via ssh, basic stuff seems to be working. Needs a lot more testing, but feel free to grab the image and try for yourself 😄

https://github.com/kttr-io/debian-lx-brand-image-builder/releases