Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Chroot to pi sd card
#!/bin/bash
# This script allows you to chroot ("work on")
# the raspbian sd card as if it's the raspberry pi
# on your Ubuntu desktop/laptop
# just much faster and more convenient
# credits: https://gist.github.com/jkullick/9b02c2061fbdf4a6c4e8a78f1312a689
# make sure you have issued
# (sudo) apt install qemu qemu-user-static binfmt-support
# Write the raspbian image onto the sd card,
# boot the pi with the card once
# so it expands the fs automatically
# then plug back to your laptop/desktop
# and chroot to it with this script.
# Invoke:
# (sudo) ./chroot-to-pi.sh /dev/sdb
# assuming /dev/sdb is your sd-card
# if you don't know, when you plug the card in, type:
# dmesg | tail -n30
# Note: If you have an image file instead of the sd card,
# you will need to issue
# (sudo) apt install kpartx
# (sudo) kpartx -v -a 2017-11-29-raspbian-stretch-lite.img
# then
# (sudo) ./chroot-to-pi.sh /dev/mapper/loop0p
# With the vanilla image, you have very little space to work on
# I have not figured out a reliable way to resize it
# Something like this should work, but it didn't in my experience
# https://gist.github.com/htruong/0271d84ae81ee1d301293d126a5ad716
# so it's better just to let the pi resize the partitions
mkdir -p /mnt/raspbian
# mount partition
mount -o rw ${1}2 /mnt/raspbian
mount -o rw ${1}1 /mnt/raspbian/boot
# mount binds
mount --bind /dev /mnt/raspbian/dev/
mount --bind /sys /mnt/raspbian/sys/
mount --bind /proc /mnt/raspbian/proc/
mount --bind /dev/pts /mnt/raspbian/dev/pts
# ld.so.preload fix
sed -i 's/^/#CHROOT /g' /mnt/raspbian/etc/ld.so.preload
# copy qemu binary
cp /usr/bin/qemu-arm-static /mnt/raspbian/usr/bin/
echo "You will be transferred to the bash shell now."
echo "Issue 'exit' when you are done."
echo "Issue 'su pi' if you need to work as the user pi."
# chroot to raspbian
chroot /mnt/raspbian /bin/bash
# ----------------------------
# Clean up
# revert ld.so.preload fix
sed -i 's/^#CHROOT //g' /mnt/raspbian/etc/ld.so.preload
# unmount everything
umount /mnt/raspbian/{dev/pts,dev,sys,proc,boot,}
@Robokishan
Copy link

Is there any way we can get kernel version of img file i just have to copy .ko compiled files for linux kernel into system. but rather than hard coding kernel version like /lib/modules/5.10.11-v7l+/ i would like to get kernel version dynamically so in future it would be easy. but the problem is uname -r provides kernel version of host os any help please

@Robokishan
Copy link

Robokishan commented Feb 17, 2021

https://gist.github.com/Robokishan/8ffb8acec88fbbaf6c6c857d9c4ffe6a made a simple script for operation
How to do

  1. Download chroot-to-pi.sh
  2. in the same directory download above script
  3. Download img file of raspberrypi
  4. bash setup-chroot.sh
  5. Once work finished type exit and all the loop device will be deleted and mounted dir will be unmounted

Expand img file

https://gist.github.com/Robokishan/4dc13947b980bdcdfc20543b75c1f0fb using this script

@gnthibault
Copy link

It might seem obvious to some, but this method work wonderfull for very simple task, but due to the very nature of systemd and the way that chroot is working, you cannot get anything related to systemd done, you will get something like this:

Running in chroot, ignoring request: start
Running in chroot, ignoring request: restart
Running in chroot, ignoring request: reload
Running in chroot, ignoring request: daemon-reload
Running in chroot, ignoring request: is-active

@cinderblock
Copy link

@gnthibault Those methods indead do not work because they do not make sense to run when the Pi is offline.

However systemctl enable ... and related configuration commands work just fine.

PS, I've combined some of the ideas here with some others into a full repo. I'd love for others to check it out!

https://github.com/cinderblock/RaspberryPi-Image-Generator

@dmuiX
Copy link

dmuiX commented Dec 4, 2022

I would add something like to establish internet connection:

# establish internet connection
mv /mnt/raspbian/etc/resolv.conf /mnt/raspbian/etc/resolv.conf_bak
cp /etc/resolv.conf /mnt/raspbian/etc/

And in the cleanup section:

# revert /etc/resolv.conf_bak
rm /mnt/raspbian/etc/resolv.conf 
mv /mnt/raspbian/etc/resolv.conf_bak /mnt/raspbian/etc/resolv.conf

Just saw that somebody above already suggested adding resolv.conf as a mount bind. I will test if this is the better way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment