Joe
February 3, 2021, 2:16am
1
A change to an upstream package is forcing us to update from the Balena base image intel-nuc-python:3.8-bullseye-build to a base image using Python 3.9. When does Balena plan on releasing an image for intel-nuc-python:3.9.1-bullseye-build?
Unfortunately when we try to build the base image ourselves from source we are running into a number of difficult errors.
# AUTOGENERATED FILE
FROM balenalib/intel-nuc-debian:bullseye-build
# remove several traces of debian python
RUN apt-get purge -y python.*
# http://bugs.python.org/issue19846
# > At the moment, setting "LANG=C" on a Linux system *fundamentally breaks Python 3*, and that's not OK.
ENV LANG C.UTF-8
# key 63C7CC90: public key "Simon McVittie <smcv@pseudorandom.co.uk>" imported
# key 3372DCFA: public key "Donald Stufft (dstufft) <donald@stufft.io>" imported
RUN gpg --batch --keyserver keyring.debian.org --recv-keys 4DE8FF2A63C7CC90 \
&& gpg --batch --keyserver keyserver.ubuntu.com --recv-key 6E3CBCE93372DCFA \
&& gpg --batch --keyserver keyserver.ubuntu.com --recv-keys 0x52a43a1e4b77b059
ENV PYTHON_VERSION 3.9.1
# if this is called "PIP_VERSION", pip explodes with "ValueError: invalid truth value '<VERSION>'"
ENV PYTHON_PIP_VERSION 20.3.1
show original
Hello,
Thanks for reporting this. It does seem there was a build error which is related to the python-dbus version we specified not being compatible with Python3.9.1. I’ve created a GH issue to track this Unable to find base image intel-nuc-python:3.9.1-bullseye-build · Issue #680 · balena-io-library/base-images · GitHub
We are updating the Dockerfile and will get back to you once the base image is available
Cheers