To begin, you'll save the Dockerfile below to a folder on your local filesystem. Name it as Dockerfile with no file extension, just like you did on the Test Image page.
# Dockerfile port of https://gist.github.com/jcmvbkbc/316e6da728021c8ff670a24e674a35e6
# wifi details http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:esp32s3wifi
# we need python 3.10 not 3.11
FROM ubuntu:22.04
RUN apt-get update
RUN apt-get -y install gperf bison flex texinfo help2man gawk libtool-bin git unzip ncurses-dev rsync zlib1g zlib1g-dev xz-utils cmake wget bzip2 g++ python3 python3-dev python3-pip cpio bc virtualenv libusb-1.0 && \
ln -s /usr/bin/python3 /usr/bin/python
WORKDIR /app
# install autoconf 2.71
RUN wget https://ftp.gnu.org/gnu/autoconf/autoconf-2.71.tar.xz && \
tar -xf autoconf-2.71.tar.xz && \
cd autoconf-2.71 && \
./configure --prefix=`pwd`/root && \
make && \
make install
ENV PATH="$PATH:/app/autoconf-2.71/root/bin"
# dynconfig
RUN git clone https://github.com/jcmvbkbc/xtensa-dynconfig -b original --depth=1 && \
git clone https://github.com/jcmvbkbc/config-esp32s3 esp32s3 --depth=1 && \
make -C xtensa-dynconfig ORIG=1 CONF_DIR=`pwd` esp32s3.so
ENV XTENSA_GNU_CONFIG="/app/xtensa-dynconfig/esp32s3.so"
# ct-ng cannot run as root, we'll just do everything else as a user
RUN useradd -d /app/build -u 3232 esp32 && mkdir build && chown esp32:esp32 build
USER esp32
# toolchain
RUN cd build && \
git clone https://github.com/jcmvbkbc/crosstool-NG.git -b xtensa-fdpic --depth=1 && \
cd crosstool-NG && \
./bootstrap && \
./configure --enable-local && \
make && \
./ct-ng xtensa-esp32s3-linux-uclibcfdpic && \
CT_PREFIX=`pwd`/builds ./ct-ng build || echo "Completed" # the complete ct-ng build fails but we still get what we wanted!
RUN [ -e build/crosstool-NG/builds/xtensa-esp32s3-linux-uclibcfdpic/bin/xtensa-esp32s3-linux-uclibcfdpic-gcc ] || exit 1
# kernel and rootfs
RUN cd build && \
git clone https://github.com/jcmvbkbc/buildroot -b xtensa-2023.02-fdpic --depth=1 && \
make -C buildroot O=`pwd`/build-xtensa-2023.02-fdpic-esp32s3 esp32s3wifi_defconfig && \
buildroot/utils/config --file build-xtensa-2023.02-fdpic-esp32s3/.config --set-str TOOLCHAIN_EXTERNAL_PATH `pwd`/crosstool-NG/builds/xtensa-esp32s3-linux-uclibcfdpic && \
buildroot/utils/config --file build-xtensa-2023.02-fdpic-esp32s3/.config --set-str TOOLCHAIN_EXTERNAL_PREFIX '$(ARCH)-esp32s3-linux-uclibcfdpic' && \
buildroot/utils/config --file build-xtensa-2023.02-fdpic-esp32s3/.config --set-str TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX '$(ARCH)-esp32s3-linux-uclibcfdpic' && \
make -C buildroot O=`pwd`/build-xtensa-2023.02-fdpic-esp32s3
RUN [ -f build/build-xtensa-2023.02-fdpic-esp32s3/images/xipImage -a -f build/build-xtensa-2023.02-fdpic-esp32s3/images/rootfs.cramfs ] || exit 1
# bootloader
ENV IDF_PATH="/app/build/esp-hosted/esp_hosted_ng/esp/esp_driver/esp-idf"
RUN cd build && \
git clone https://github.com/jcmvbkbc/esp-hosted -b shmem --depth=1 && \
cd esp-hosted/esp_hosted_ng/esp/esp_driver && cmake . && \
cd esp-idf && . ./export.sh && \
cd ../network_adapter && idf.py set-target esp32s3 && \
cp sdkconfig.defaults.esp32s3 sdkconfig && idf.py build
# move files over
RUN cd build && mkdir release && \
cp esp-hosted/esp_hosted_ng/esp/esp_driver/network_adapter/build/bootloader/bootloader.bin release && \
cp esp-hosted/esp_hosted_ng/esp/esp_driver/network_adapter/build/partition_table/partition-table.bin release && \
cp esp-hosted/esp_hosted_ng/esp/esp_driver/network_adapter/build/network_adapter.bin release && \
cp build-xtensa-2023.02-fdpic-esp32s3/images/xipImage release && \
cp build-xtensa-2023.02-fdpic-esp32s3/images/rootfs.cramfs release
# keep docker running so we can debug/rebuild :)
USER root
ENTRYPOINT ["tail", "-f", "/dev/null"]
# grab the files with `docker cp CONTAINER_NAME:/app/build/release/\* .`
# now you can burn the files from the 'release' folder with:
# python esptool.py --chip esp32s3 -p /dev/ttyUSB0 -b 921600 --before=default_reset --after=hard_reset write_flash 0x0 bootloader.bin 0x10000 network_adapter.bin 0x8000 partition-table.bin
# next we can burn in the kernel and filesys with parttool, which is part of esp-idf
# parttool.py write_partition --partition-name linux --input xipImage
# parttool.py write_partition --partition-name rootfs --input rootfs.cramfs
As you can see, this Dockerfile is a lot more detailed than the test image that you just ran. It installs all of the toolchains and dependencies on an Ubuntu build and then runs the script to compile the files needed to load onto the ESP32-S3.
The steps for building are the same though. Open a terminal window, navigate to the folder where you saved the Dockerfile and enter:
docker build -t esp32-s3_linux .
This builds the image and names it esp32-s3_linux.
After building, go to the Docker desktop app and look under Images. Select your newly created esp32-s3_linux image and click the Play button. Then click Run to start a container with the image.
Once the container opens, go to the Terminal tab. You'll be able to interact with the Ubuntu machine that has your compiled files for the ESP32-S3.
If you change directories to the releases folder (cd /app/build/releases) you'll see the kernel, file system and binary files that will be loaded onto your ESP32-S3. To use these files, you'll need to copy them to your local filesystem out of the Docker container.
To do this, go back to a terminal window on your local desktop and navigate to the directory where you saved the Dockerfile. Enter the following command:
docker cp CONTAINER-NAME:/app/build/release/ bin_files
Replace CONTAINER-NAME with the name of your container in the Docker app. This copies the /release folder from your container in Docker to a folder called /bin_files.
Text editor powered by tinymce.
