Re: With F36 systemd-nspawn test environment not usable, no login possible

2022-07-07 Thread Petr Pisar
V Tue, Jul 05, 2022 at 09:29:14AM +0200, Lennart Poettering napsal(a): > On Di, 05.07.22 14:38, Dominique Martinet (asmad...@codewreck.org) wrote: > > you'll see it complain that there is no /bin/login: you just need to > > install util-linux (or possibly busybox) and you'll get a prompt, > >

Re: With F36 systemd-nspawn test environment not usable, no login possible

2022-07-05 Thread Lennart Poettering
On Di, 05.07.22 14:38, Dominique Martinet (asmad...@codewreck.org) wrote: > Peter Boy wrote on Tue, Jul 05, 2022 at 07:19:28AM +0200: > > […]# dnf --releasever=36 --best --setopt=install_weak_deps=False \ > > --installroot=/var/lib/machines/testf36 install dhcp-client dnf \ > >

Re: With F36 systemd-nspawn test environment not usable, no login possible

2022-07-05 Thread Peter Boy
> Am 05.07.2022 um 07:38 schrieb Dominique Martinet : > > Peter Boy wrote on Tue, Jul 05, 2022 at 07:19:28AM +0200: >> […]# dnf --releasever=36 --best --setopt=install_weak_deps=False \ >>--installroot=/var/lib/machines/testf36 install dhcp-client dnf \ >>fedora-release glibc

Re: With F36 systemd-nspawn test environment not usable, no login possible

2022-07-04 Thread Dominique Martinet
Peter Boy wrote on Tue, Jul 05, 2022 at 07:19:28AM +0200: > […]# dnf --releasever=36 --best --setopt=install_weak_deps=False \ > --installroot=/var/lib/machines/testf36 install dhcp-client dnf \ > fedora-release glibc glibc-langpack-en iputils less ncurses passwd \ > systemd

With F36 systemd-nspawn test environment not usable, no login possible

2022-07-04 Thread Peter Boy
We use a systemd-nspawn container to set up a test environment, among others. With F36 this is currently not workable for us because the login process is broken. I set up a container as usual using dnf to create a container file system, e.g. using […]# dnf --releasever=36 --best