You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This only seems to affect Bullseye and not Buster (legacy), or at least Buster 2022-04-07 is not affected.
Technically speaking, on first boot the "first-boot wizard" should jump and ask for a username and password, which could be automated with expect. However, with dockerpi the you end up in a step asking for username and password (maybe because the serial console is via tty?):
[ OK ] Started Authorization Manager.
Raspbian GNU/Linux 11 raspberrypi ttyAMA0
raspberrypi login:
The workaround would be to add a userconf/userconf.txt file in the boot partition, with a username and password (more info in the link above).
To do that in automation the simplest thing might be to create a bash script and run it inside a docker container (mounting the image and script inside), as the intructions will be very much OS specific.
The text was updated successfully, but these errors were encountered:
I'm trying to automate creation of an image for a Pi B. The above was my thought for adding a user [back] in to the image. fdisk to find the sector start and then mount the linux partition, add the userconf file. Unless I'm doing something stupid, can't get this to work. Even copied an existing password from /etc/shadow.
The April 2022 release has removed the default
pi
username from Raspberry Pi OS:https://www.raspberrypi.com/news/raspberry-pi-bullseye-update-april-2022/
This only seems to affect Bullseye and not Buster (legacy), or at least Buster 2022-04-07 is not affected.
Technically speaking, on first boot the "first-boot wizard" should jump and ask for a username and password, which could be automated with
expect
. However, withdockerpi
the you end up in a step asking for username and password (maybe because the serial console is via tty?):The workaround would be to add a
userconf
/userconf.txt
file in the boot partition, with a username and password (more info in the link above).To do that in automation the simplest thing might be to create a bash script and run it inside a docker container (mounting the image and script inside), as the intructions will be very much OS specific.
The text was updated successfully, but these errors were encountered: