With F36 systemd-nspawn test environment not usable, no login
possible
by 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 --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 systemd-networkd vim-default-editor
I can set a password using
[…]# systemd-nspawn -D /var/lib/machines/testf36 passwd
I create a container with
[…]# systemd-nspawn -D /var/lib/machines/testf36 -b
The container starts fine and finally displays a login prompt. You can enter a name as usual. There follows no password prompt, but after a while it still displays a login prompt again.
The container even keeps running if I exit the login process (is shows up in machinectl).
It’s not a SELinux issue, the system was in permissive mode.
If I start a system service container using
[…]# systemctl systemd-nspawn@testf36
the container start fine, shows up in machinectl, but a
[…]# machinectl login testf36
produces the same phenomenon of repeated display of the login prompt without asking for the password.
And
[…]# machinectl shell testf36
results in „Connection to machine testf36 terminated.“
== My questions: ==
* Does anyone has the same problem
* or does anyone use a F36 systemd-nspawn container without such a problems?
* Or did I miss a change, so I have to use a different procedure?
Several releases ago we had a similar issue because auf /etc/securetty, but that doesn’t exist anymore.
A F35 container works fine on a F36 host. But a F36 container doesn’t work on a F35 host either.
1 year, 10 months
Fedora CoreOS Meeting Minutes 2022-07-06
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-07-06/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-07-06/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-07-06/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:13 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-07-06/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:18)
* Action items from last meeting (dustymabe, 16:33:42)
* ACTION: jlebon to open investigation tickets for the IMA/FIDO
changes (dustymabe, 16:35:19)
* there was an existing ticket for becoming an edition
(https://github.com/coreos/fedora-coreos-tracker/issues/915) and
cverna opened a ticket related to becoming an edition
(https://github.com/coreos/fedora-coreos-tracker/issues/1239).
(dustymabe, 16:36:42)
* New Package Request: Crash (dustymabe, 16:37:42)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1238
(dustymabe, 16:37:46)
* AGREED: We don't think including the crash program in Fedora CoreOS
is extremely useful because it needs the kernel-debuginfo packages
in order to do crash dump analysis and you can grab crash at the
same time those packages are downloaded. Though, we do think it
would be useful to document how to do the crashdump analysis from
say a toolbox container. (dustymabe, 16:54:00)
* installing non-x86_64 emulators (dustymabe, 16:55:36)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1237
(dustymabe, 16:55:40)
* AGREED: We included the x86_64 emulator on non-x86_64 architectures
to get access to the large library of containers that are only built
for x86_64 today. We don't think there is a significant enough user
base wanting aarch64/ppc64le/s390x emulators for containers built
just for those architectures (usually if you are building for
aarch64/ppc64le/s390x you are building for all (dustymabe,
17:09:10)
* tracker: Fedora 37 changes considerations (dustymabe, 17:09:21)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1222
(dustymabe, 17:09:26)
* open floor (dustymabe, 17:23:54)
Meeting ended at 17:31:11 UTC.
Action Items
------------
* jlebon to open investigation tickets for the IMA/FIDO changes
Action Items, by person
-----------------------
* jlebon
* jlebon to open investigation tickets for the IMA/FIDO changes
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (110)
* jlebon (30)
* zodbot (19)
* lucab (15)
* jdoss (14)
* jbrooks (7)
* jmarrero (7)
* walters (4)
* gursewak (2)
* ravanelli (1)
* lorbus (1)
* mnguyen (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 10 months
Retired: python-contextlib2
by Ali Erdinc Koroglu
Dear maintainers,
I have retired python-contextlib2 on rawhide, for details please read
the link.
https://bugzilla.redhat.com/show_bug.cgi?id=2019014
BR,
Ali
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
1 year, 10 months
Bugzilla Assignee
by Jamie Nguyen
Hi,
I was wondering if someone could help me.
I stopped (co-)maintaining weechat and adobe-source-code-pro-fonts
several years ago, but I discovered I'm still listed as the Bugzilla
Assignee for EPEL on both packages [1][2] despite not have commit
access. (FAS username: jamielinux)
I contacted the current maintainers 3 months ago but didn't get a
response so I thought I'd try here.
Could someone please set the Bugzilla Assignee for EPEL for both
packages to match the main Bugzilla Assignee?
Thank you!
[1]: https://src.fedoraproject.org/rpms/weechat
[2]: https://src.fedoraproject.org/rpms/adobe-source-code-pro-fonts
Kind regards,
Jamie
1 year, 10 months
