Skip to content

Commit b0c595e

Browse files
committed
fix(docker): python bytecode compilation
- we were seeing some issues when building the uboot containers with bytecode compilation, especially on Ubuntu Noble - apparently this is common and known problem - there are multiple possible workarounds, one is to postpone the automatic bytecode compilation, but this is problematic because our containers are multi-arch (x86_64 and arm64) - bump ubuntu to Plucky Puffin (25.04) Signed-off-by: AtomicFS <vojtech.vesely@9elements.com>
1 parent 5a8555e commit b0c595e

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

docker/uboot/Dockerfile

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# This is multi-stage Dockerfile
22
# Docs: https://docs.docker.com/build/building/multi-stage/
33

4-
ARG SOURCE_IMAGE=ubuntu:noble
4+
ARG SOURCE_IMAGE=ubuntu:plucky
55
ARG TARGETARCH=amd64
66

77
#=============
@@ -18,10 +18,6 @@ ENV VERIFICATION_TEST_UBOOT_VERSION=v${UBOOT_VERSION}
1818

1919
ENV DEBIAN_FRONTEND=noninteractive
2020

21-
# Ubuntu Noble has issues with Python bytecode compilation
22-
# Disable automatic .pyc compilation during install, and later run it manually
23-
ENV DEB_PYTHON_INSTALL_LAYOUT=deb
24-
2521
RUN apt-get update && \
2622
apt-get install -y --no-install-recommends \
2723
bc \
@@ -66,7 +62,6 @@ RUN apt-get update && \
6662
python3-virtualenv \
6763
swig \
6864
uuid-dev \
69-
&& python3 -m compileall /usr/lib/python3/dist-packages \
7065
&& \
7166
if [ "${TARGETARCH}" = 'amd64' ]; then \
7267
apt-get install -y --no-install-recommends \

0 commit comments

Comments
 (0)