matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
681c24878b
sonic-buildimage/sonic-slave-bullseye/Dockerfile.j2

535 lines
18 KiB
Docker
Raw Normal View History

Add a config variable to override default container registry instead of dockerhub. (#10166) * Add variable to reset default docker registry * fix bug in docker version control
2022-03-14 05:09:20 -05:00
{% set prefix = DEFAULT_CONTAINER_REGISTRY %}
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
{%- if CONFIGURED_ARCH == "armhf" and MULTIARCH_QEMU_ENVIRON == "y" %}
Add a config variable to override default container registry instead of dockerhub. (#10166) * Add variable to reset default docker registry * fix bug in docker version control
2022-03-14 05:09:20 -05:00
FROM {{ prefix }}multiarch/qemu-user-static:x86_64-arm-6.1.0-8 as qemu
FROM {{ prefix }}multiarch/debian-debootstrap:armhf-bullseye
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
COPY --from=qemu /usr/bin/qemu-arm-static /usr/bin
{%- elif CONFIGURED_ARCH == "arm64" and MULTIARCH_QEMU_ENVIRON == "y" %}
Add a config variable to override default container registry instead of dockerhub. (#10166) * Add variable to reset default docker registry * fix bug in docker version control
2022-03-14 05:09:20 -05:00
FROM {{ prefix }}multiarch/qemu-user-static:x86_64-aarch64-6.1.0-8 as qemu
FROM {{ prefix }}multiarch/debian-debootstrap:arm64-bullseye
Update Centec platform support for Bullseye and 5.10 kernel (#7) 1. Fix build for armhf and arm64 2. upgrade centec tsingma bsp support to 5.10 kernel 3. modify centec platform driver for linux 5.10 Co-authored-by: Shi Lei <shil@centecnetworks.com>
2021-10-25 17:36:55 -05:00
COPY --from=qemu /usr/bin/qemu-aarch64-static /usr/bin
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
{%- else -%}
Add a config variable to override default container registry instead of dockerhub. (#10166) * Add variable to reset default docker registry * fix bug in docker version control
2022-03-14 05:09:20 -05:00
FROM {{ prefix }}debian:bullseye
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
{%- endif %}
MAINTAINER gulv@microsoft.com
COPY ["no-check-valid-until", "/etc/apt/apt.conf.d/"]
## TODO: Re-add in any necessary mirror URLs here as they become available
RUN echo "deb [arch=amd64] http://debian-archive.trafficmanager.net/debian/ bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=amd64] http://debian-archive.trafficmanager.net/debian/ bullseye main contrib non-free" >> /etc/apt/sources.list && \
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
echo "deb [arch=amd64] http://debian-archive.trafficmanager.net/debian-security/ bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=amd64] http://debian-archive.trafficmanager.net/debian-security/ bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
[Build]: fix debian package not found issue (#10447) Why I did it [Build]: fix debian package not found issue
2022-04-06 00:51:41 -05:00
echo "deb [arch=amd64] http://debian-archive.trafficmanager.net/debian bullseye-backports main" >> /etc/apt/sources.list && \
echo "deb [arch=amd64] http://packages.trafficmanager.net/debian/debian bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb [arch=amd64] http://packages.trafficmanager.net/debian/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
{%- if CONFIGURED_ARCH == "armhf" %}
RUN echo "deb [arch=armhf] http://deb.debian.org/debian bullseye main contrib non-free" > /etc/apt/sources.list && \
echo "deb-src [arch=armhf] http://deb.debian.org/debian bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb [arch=armhf] http://deb.debian.org/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=armhf] http://deb.debian.org/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list && \
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
echo "deb [arch=armhf] http://security.debian.org bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=armhf] http://security.debian.org bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
echo 'deb [arch=armhf] http://ftp.debian.org/debian bullseye-backports main' >> /etc/apt/sources.list && \
echo "deb [arch=armhf] http://packages.trafficmanager.net/debian/debian bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb [arch=armhf] http://packages.trafficmanager.net/debian/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list
{%- elif CONFIGURED_ARCH == "arm64" %}
RUN echo "deb [arch=arm64] http://deb.debian.org/debian bullseye main contrib non-free" > /etc/apt/sources.list && \
echo "deb-src [arch=arm64] http://deb.debian.org/debian bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb [arch=arm64] http://deb.debian.org/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=arm64] http://deb.debian.org/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list && \
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
echo "deb [arch=arm64] http://security.debian.org bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
echo "deb-src [arch=arm64] http://security.debian.org bullseye-security main contrib non-free" >> /etc/apt/sources.list && \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
echo 'deb [arch=arm64] http://ftp.debian.org/debian bullseye-backports main' >> /etc/apt/sources.list && \
echo "deb [arch=arm64] http://packages.trafficmanager.net/debian/debian bullseye main contrib non-free" >> /etc/apt/sources.list && \
echo "deb [arch=arm64] http://packages.trafficmanager.net/debian/debian bullseye-updates main contrib non-free" >> /etc/apt/sources.list
{%- endif %}
## Make apt-get non-interactive
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y \
apt-utils \
default-jre-headless \
openssh-server \
curl \
wget \
unzip \
git \
build-essential \
libtool \
lintian \
sudo \
dh-make \
dh-exec \
kmod \
libtinyxml2-dev \
python3 \
python3-pip \
libncurses5-dev \
texinfo \
dh-autoreconf \
doxygen \
devscripts \
git-buildpackage \
perl-modules \
libswitch-perl \
libzmq5 \
libzmq3-dev \
jq \
Add cron and the python 3 mock packages to the Bullseye slave image When using dpkg with the --root flag to install a deb package in a chroot, dpkg checks to see if the users and groups specified in the /var/lib/dpkg/statoverride file are valid. The problem is, it checks against the host system's /etc/passwd and /etc/group files, instead of /etc/passwd and /etc/group inside the chroot. In the slave image for Buster, cron appears to have been automatically installed, and so the crontab group existed. This doesn't appear to be true for Bullseye, so explicitly install it. This makes sure that the crontab group exists on the slave image itself. Also install the mock python 3 package, this is needed by some test. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-07-23 11:28:36 -05:00
cron \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For quagga build
libreadline-dev \
texlive-latex-base \
texlive-plain-generic \
texlive-fonts-recommended \
libpam0g-dev \
libpam-dev \
libcap-dev \
imagemagick \
ghostscript \
groff \
libpcre3-dev \
gawk \
chrpath \
# For frr build
libc-ares-dev \
libsnmp-dev \
libjson-c-dev \
libsystemd-dev \
python3-ipaddr \
libcmocka-dev \
python3-all-dev \
python3-all-dbg \
install-info \
logrotate \
# For libnl3 (local) build
cdbs \
# For SAI meta build
libxml-simple-perl \
graphviz \
aspell \
# For linux build
bc \
fakeroot \
build-essential \
devscripts \
quilt \
stgit \
secureboot: Enable signing SONiC kernel (#10557) Why I did it To sign SONiC kernel image and allow secure boot based system to verify SONiC image before loading into the system. How I did it Pass following parameter to rules/config.user Ex: SONIC_ENABLE_SECUREBOOT_SIGNATURE := y SIGNING_KEY := /path/to/key/private.key SIGNING_CERT := /path/to/public/public.cert How to verify it Secure boot enabled system enrolled with right public key of the, image in the platform UEFI database will able to verify image before load. Alternatively one can verify with offline sbsign tool as below. export SBSIGN_KEY=/abc/bcd/xyz/ sbverify --cert $SBSIGN_KEY/public_cert.cert fsroot-platform-XYZ/boot/vmlinuz-5.10.0-8-2-amd64 mage O/P: Signature verification OK
2022-04-19 00:23:15 -05:00
sbsigntool \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For platform-modules build
module-assistant \
# For thrift build\
gem2deb \
libevent-dev \
libglib2.0-dev \
python3-all-dev \
python3-twisted \
phpunit \
libbit-vector-perl \
openjdk-11-jdk \
javahelper \
maven-debian-helper \
ant \
libhttpclient-java \
libslf4j-java \
libservlet3.1-java \
pkg-php-tools \
# For mellanox sdk build
libpcre3 \
libpcre3-dev \
byacc \
flex \
libglib2.0-dev \
bison \
expat \
libexpat1-dev \
dpatch \
libdb-dev \
libiptc-dev \
libxtables-dev \
# For mellanox sai build
libtool-bin \
libxml2-dev \
# For BFN sdk build
libusb-1.0-0-dev \
libcurl3-nss-dev \
libunwind8-dev \
telnet \
libc-ares2 \
libgoogle-perftools4 \
# For build image
cpio \
squashfs-tools \
zip \
# For broadcom sdk build
{%- if CONFIGURED_ARCH == "amd64" %}
linux-compiler-gcc-10-x86 \
{%- endif %}
{%- if CONFIGURED_ARCH == "armhf" %}
linux-compiler-gcc-10-arm \
{%- endif %}
linux-kbuild-5.10 \
# teamd build
libdaemon-dev \
libdbus-1-dev \
libjansson-dev \
# For cavium sdk build
libpcap-dev \
dnsutils \
libusb-dev \
# For debian image reconfiguration
augeas-tools \
# For p4 build
libyaml-dev \
libevent-dev \
libjudy-dev \
libedit-dev \
libnanomsg-dev \
python3-stdeb \
# For redis build
libjemalloc-dev \
liblua5.1-0-dev \
lua-bitop-dev \
lua-cjson-dev \
# For mft kernel module build
dkms \
# For Jenkins static analysis, unit testing and code coverage
cppcheck \
clang \
pylint \
python3-pytest \
Update Barefoot platform module for Bullseye and 5.10 kernel (#8) Update Barefoot platform support for Bullseye and 5.10 kernel, and add python3-venv.
2021-10-28 22:19:53 -05:00
python3-venv \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
gcovr \
python3-pytest-cov \
python3-pytest-cov \
python3-parse \
# For snmpd
default-libmysqlclient-dev \
libssl-dev \
libperl-dev \
libpci-dev \
libpci3 \
libsensors5 \
libsensors4-dev \
libwrap0-dev \
# For lldpd
debhelper \
autotools-dev \
libbsd-dev \
pkg-config \
check \
# For mpdecimal
docutils-common \
libjs-sphinxdoc \
libjs-underscore \
python3-docutils \
python3-jinja2 \
python3-markupsafe \
python3-pygments \
python3-roman \
python3-sphinx \
sphinx-common \
python3-sphinx \
# For sonic config engine testing
python3-dev \
{%- if CONFIGURED_ARCH == "armhf" or CONFIGURED_ARCH == "arm64" %}
libxslt-dev \
{%- endif %}
# For lockfile
procmail \
# For gtest
libgtest-dev \
cmake \
[sonic-slave]: Add gmock for sonic-swss-common tests (#8950) Sonic-swss-common requires gmock for staged unit tests Signed-off-by: Don Newton <don@opennetworking.org>
2021-10-28 14:14:21 -05:00
# For gmock
libgmock-dev \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For pam_tacplus build
autoconf-archive \
# For iproute2
cm-super-minimal \
libatm1-dev \
libelf-dev \
libmnl-dev \
libselinux1-dev \
linuxdoc-tools \
lynx \
texlive-latex-extra \
texlive-latex-recommended \
iproute2 \
# For bash
texi2html \
[TACACS+] Add plugin support to bash. (#8660) This pull request add plugin support library to bash. And we will create a TACACS+ plugin for bash in an other PR, which will bring per command authorization feature to bash. Why I did it To support TACACS per command authorization, we check user command before execute it. How I did it Add plugin support to bash. How to verify it UT with CUnit under bash project cover all new code in plugin.c. Also pass all current UT. Which release branch to backport (provide reason below if selected) N/A Description for the changelog Add plugin support to bash.
2021-10-11 02:20:51 -05:00
sharutils \
locales \
time \
man2html-base \
libcunit1 \
libcunit1-dev \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For initramfs
shellcheck \
bash-completion \
{%- if CONFIGURED_ARCH == "amd64" %}
# For sonic vs image build
dosfstools \
qemu-kvm \
libvirt-clients \
{%- endif %}
# For ntp
autogen \
libopts25-dev \
pps-tools \
dh-apparmor \
# For lm-sensors
librrd8 \
librrd-dev \
rrdtool \
# For kdump-tools
liblzo2-dev \
# For iptables
libnetfilter-conntrack-dev \
libnftnl-dev \
# For SAI3.7
protobuf-compiler \
libprotobuf-dev \
xxd \
# For DHCP Monitor tool
libexplain-dev \
libevent-dev \
# For libyang
swig \
# For build dtb
device-tree-compiler \
# For sonic-mgmt-framework
autoconf \
m4 \
libxml2-utils \
xsltproc \
python3-lxml \
libexpat1-dev \
libcurl3-gnutls \
libcjson-dev \
# For WPA supplication
qtbase5-dev \
aspell-en \
libssl-dev \
dbus \
libdbus-1-dev \
libdbus-glib-1-2 \
libdbus-glib-1-dev \
libreadline-dev \
libncurses5-dev \
libpcsclite-dev \
docbook-to-man \
docbook-utils \
# For kdump-tools
libbz2-dev \
# For linkmgrd
[docker-dhcprelay]: Update to Bullseye (#9736) As part of this, update the isc-dhcp package to match the Bullseye version (this fixes some compile errors related to BIND), clean up some of the build dependencies and runtime dependencies for debian packaging, and use the default Boost version to compile against instead of explicitly saying using 1.74. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2022-01-18 17:11:36 -06:00
libboost-dev \
libboost-program-options-dev \
libboost-system-dev \
libboost-thread-dev \
libboost-atomic-dev \
libboost-chrono-dev \
libboost-container-dev \
libboost-context-dev \
libboost-contract-dev \
libboost-coroutine-dev \
libboost-date-time-dev \
libboost-fiber-dev \
libboost-filesystem-dev \
libboost-graph-parallel-dev \
libboost-log-dev \
libboost-regex-dev \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
googletest \
libgtest-dev \
Add `libgmock` package for `linkmgrd` (#10294) Why I did it Add libgmock-dev to the package list required by linkmgrd unittests. Required by PR: Azure/sonic-linkmgrd#45 How I did it Add the package to the package list. How to verify it Build docker-mux with KEEP_SLAVE_ON=yes and verify libgmock-dev is present. Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
2022-04-13 19:59:54 -05:00
libgmock-dev \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
libgcc-10-dev \
# For sonic-host-services build
libcairo2-dev \
libdbus-1-dev \
libgirepository1.0-dev \
libsystemd-dev \
[TACACS+] Add audisp-tacplus for per-command accounting. (#8750) This pull request integrate audisp-tacplus to SONiC for per-command accounting. #### Why I did it To support TACACS per-command accounting, we integrate audisp-tacplus project to sonic. #### How I did it 1. Add auditd service to SONiC 2. Port and patch audisp-tacplus to SONiC #### How to verify it UT with CUnit to cover all new code in usersecret-filter.c Also pass all current UT. #### Which release branch to backport (provide reason below if selected) N/A #### Description for the changelog Add audisp-tacplus for per-command accounting. #### A picture of a cute animal (not mandatory but encouraged)
2021-11-30 21:50:09 -06:00
pkg-config \
# For audisp-tacplus
libauparse-dev \
auditd
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
[openssh]: add build dep installation to sonic-slave-bullseye This is the continuation of PR 8381 and is needed for debian 11 build. Signed-off-by: Guohan Lu <lguohan@gmail.com>
2021-08-10 03:37:19 -05:00
RUN apt-get -y build-dep openssh
Update Centec platform support for Bullseye and 5.10 kernel (#7) 1. Fix build for armhf and arm64 2. upgrade centec tsingma bsp support to 5.10 kernel 3. modify centec platform driver for linux 5.10 Co-authored-by: Shi Lei <shil@centecnetworks.com>
2021-10-25 17:36:55 -05:00
# Build fix for ARM64 and ARMHF /etc/debian_version
{%- if CONFIGURED_ARCH == "armhf" or CONFIGURED_ARCH == "arm64" %}
RUN apt upgrade -y base-files
{%- endif %}
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# Build fix for ARMHF bullseye libsairedis
{%- if CONFIGURED_ARCH == "armhf" %}
# Install doxygen build dependency packages
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
RUN apt install -y libxapian-dev yui-compressor texlive-extra-utils \
texlive-font-utils rdfind llvm-11-dev libclang-11-dev sassc faketime mat2
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# Update doxygen with 64bit file offset patch
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
RUN dget -u http://deb.debian.org/debian/pool/main/d/doxygen/doxygen_1.9.1-2.dsc && \
cd doxygen-1.9.1 && \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
sed -i '56 a add_definitions(-D_FILE_OFFSET_BITS=64)' CMakeLists.txt && \
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -b && \
cd .. && \
Update repos for Bullseye slave container Update the repos for amd64, and add support for at least arm64. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-09-06 01:02:30 -05:00
dpkg -i ./doxygen_1.9.1-2_armhf.deb && \
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
rm -fr doxygen*
# Aspell is unable to locate the language dictionaries.
# Re-installing aspell-en dictionary to fix it.
RUN apt-get install --reinstall -y aspell-en
# workaround because of https://bugs.launchpad.net/qemu/+bug/1805913, just disable aspell
[build]: marvell-armhf bullseye fixes (#9243) This commit fixes/avoids the following errors encountered during the marvell-armhf build for bullseye - Fix Marvell prestera DMA driver build failure due to kallsyms_lookup_name() no longer being exported by the updated bullseye kernel. This is a temporary fix that will be replaced by a future version of the DMA driver. - Update qemu-user-static version to align with the new glibc version included in bullseye - Skip systemd-sonic-generator unit tests to avoid test failures. Root cause is still TBD #### Why I did it Fix the following build errors observed when building marvell-armhf for bullseye 1. Marvell Prestera DMA driver uses kernel API no longer exported ERROR: modpost: "kallsyms_lookup_name" [/sonic/platform/marvell-armhf/prestera/mrvl-prestera/cpssEnabler/linuxNoKernelModule/drivers//mvDmaDrv.ko] undefined! 2. Old qemu-user-static version does not support semop() leading to following build failure semop(1): encountered an error: Function not implemented 3. systemd-sonic-generator unit test failure ssg-test.cc:217: Failure Expected equality of these values: find_string_in_file(str_t, target, num_asics) Which is: false expected_result Which is: true Error validating Before=single_inst.service in test.service [ FAILED ] SsgMainTest.ssg_main_40_npu (20 ms) [----------] 4 tests from SsgMainTest (36 ms total) [----------] Global test environment tear-down [==========] 10 tests from 3 test suites ran. (54 ms total) [ PASSED ] 7 tests. [ FAILED ] 3 tests, listed below: [ FAILED ] SsgMainTest.ssg_main_single_npu [ FAILED ] SsgMainTest.ssg_main_10_npu [ FAILED ] SsgMainTest.ssg_main_40_npu 3 FAILED TESTS
2021-11-13 12:48:58 -06:00
# Issue now being tracked here - https://gitlab.com/qemu-project/qemu/-/issues/263
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
RUN cp /bin/true /usr/bin/aspell
{%- endif %}
## Config dpkg
## install the configuration file if it’s currently missing
RUN sudo augtool --autosave "set /files/etc/dpkg/dpkg.cfg/force-confmiss"
## combined with confold: overwrite configuration files that you have not modified
RUN sudo augtool --autosave "set /files/etc/dpkg/dpkg.cfg/force-confdef"
## do not modify the current configuration file, the new version is installed with a .dpkg-dist suffix
RUN sudo augtool --autosave "set /files/etc/dpkg/dpkg.cfg/force-confold"
# For linux build
RUN apt-get -y build-dep linux
# For gobgp and telemetry build
RUN export VERSION=1.14.2 \
{%- if CONFIGURED_ARCH == "armhf" %}
&& wget https://storage.googleapis.com/golang/go$VERSION.linux-armv6l.tar.gz \
&& tar -C /usr/local -xzf go$VERSION.linux-armv6l.tar.gz \
{%- elif CONFIGURED_ARCH == "arm64" %}
&& wget https://storage.googleapis.com/golang/go$VERSION.linux-arm64.tar.gz \
&& tar -C /usr/local -xzf go$VERSION.linux-arm64.tar.gz \
{%- else %}
&& wget https://storage.googleapis.com/golang/go$VERSION.linux-amd64.tar.gz \
&& tar -C /usr/local -xzf go$VERSION.linux-amd64.tar.gz \
{%- endif %}
&& echo 'export GOROOT=/usr/local/go' >> /etc/bash.bashrc \
&& echo 'export PATH=$PATH:$GOROOT/bin' >> /etc/bash.bashrc \
&& rm go$VERSION.linux-*.tar.gz
RUN pip3 install --upgrade pip
RUN apt-get purge -y python3-pip python3-yaml
# For building Python packages
RUN pip3 install setuptools==49.6.00
RUN pip3 install wheel==0.35.1
# For building sonic-utilities
Add cron and the python 3 mock packages to the Bullseye slave image When using dpkg with the --root flag to install a deb package in a chroot, dpkg checks to see if the users and groups specified in the /var/lib/dpkg/statoverride file are valid. The problem is, it checks against the host system's /etc/passwd and /etc/group files, instead of /etc/passwd and /etc/group inside the chroot. In the slave image for Buster, cron appears to have been automatically installed, and so the crontab group existed. This doesn't appear to be true for Bullseye, so explicitly install it. This makes sure that the crontab group exists on the slave image itself. Also install the mock python 3 package, this is needed by some test. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-07-23 11:28:36 -05:00
RUN pip3 install fastentrypoints mock
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For running Python unit tests
RUN pip3 install pytest-runner==5.2
RUN pip3 install nose==1.3.7
RUN pip3 install mockredispy==2.9.3
# For p4 build
RUN pip3 install \
ctypesgen==1.0.2 \
crc16
# For sonic config engine testing
# Install pyangbind here, outside sonic-config-engine dependencies, as pyangbind causes enum34 to be installed.
# enum34 causes Python 're' package to not work properly as it redefines an incompatible enum.py module
# https://github.com/robshakir/pyangbind/issues/232
RUN pip3 install pyangbind==0.8.1
RUN pip3 uninstall -y enum34
# For templating
RUN pip3 install j2cli==0.3.10
# For sonic-mgmt-framework
RUN pip3 install "PyYAML==5.4.1"
RUN pip3 install "lxml==4.6.2"
# For sonic-platform-common testing
Revert "[sonic-slave]: Fix redis version during pip3 install (#9317)" (#9704) Reverts Azure/sonic-buildimage#9317 Since upstream fixed the issue https://github.com/redis/redis-py/pull/1726 We can continue use latest version on master branch. Fixes https://github.com/Azure/sonic-buildimage/issues/9318
2022-01-09 20:24:07 -06:00
RUN pip3 install redis
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# For vs image build
RUN pip3 install pexpect==4.8.0
# For sonic-swss-common testing
RUN pip3 install Pympler==0.8
# For sonic_yang_model build
RUN pip3 install pyang==2.4.0
# For mgmt-framework build
RUN pip3 install mmh3==2.5.1
RUN pip3 install parameterized==0.8.1
RUN apt-get install -y xsltproc
# Install dependencies for isc-dhcp-relay build
RUN apt-get -y build-dep isc-dhcp
# Install vim
RUN apt-get install -y vim
# Install rsyslog
RUN apt-get install -y rsyslog
RUN cd /usr/src/gtest && cmake . && make -C /usr/src/gtest
RUN mkdir /var/run/sshd
EXPOSE 22
# Install depot-tools (for git-retry)
RUN git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git /usr/share/depot_tools
ENV PATH /usr/share/depot_tools:$PATH
[docker-dhcprelay]: Update to Bullseye (#9736) As part of this, update the isc-dhcp package to match the Bullseye version (this fixes some compile errors related to BIND), clean up some of the build dependencies and runtime dependencies for debian packaging, and use the default Boost version to compile against instead of explicitly saying using 1.74. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2022-01-18 17:11:36 -06:00
# Install dependencies for dhcp relay test
RUN pip3 install parameterized==0.8.1
RUN pip3 install pyfakefs
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
# Install docker engine 20.10 inside docker and enable experimental feature
RUN apt-get update
RUN apt-get install -y \
apt-transport-https \
ca-certificates \
curl \
gnupg2 \
software-properties-common
{%- if CONFIGURED_ARCH == "armhf" %}
RUN update-ca-certificates --fresh
{%- endif %}
RUN curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
RUN add-apt-repository \
"deb [arch={{ CONFIGURED_ARCH }}] https://download.docker.com/linux/debian \
$(lsb_release -cs) \
stable"
RUN apt-get update
Update Docker to 20.10.14 (#10677) * Upgrade docker version from 20.10.7 to 20.10.14, and pin containerd.io Update the Docker engine version from 20.10.7 to 20.10.14. This brings in some CVE and bug fixes. Additionally, pin the version of containerd.io to a specific version, mainly for consistency/reproducibility. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Remove the containerd ordering change to docker.service This appears to be already present in the current docker.service. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Remove use of apt-key apt-key is considered deprecated, and the current practice is to just add the key into /etc/apt/trusted.gpg.d/. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Upgrade docker container in Bullseye slave to 20.10.14 Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2022-04-27 12:20:42 -05:00
RUN apt-get install -y docker-ce=5:20.10.14~3-0~debian-bullseye docker-ce-cli=5:20.10.14~3-0~debian-bullseye containerd.io=1.5.11-1
Define the Bullseye-based slave container This will be used to build our image as well as tools that need to go into this image. Notable changes from Buster: * Python 2/pip2 module installations have been removed, since nothing besides the main Python 2 binary (and virtualenv support) is now available through Bullseye. * In the cases where both the main library package and the development package are being installed, now, only the dev package is specified. The main library is typically marked as a dependency of the dev package. This reduces the number of changes we have to make as SONAMEs change. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
2021-06-22 10:33:42 -05:00
RUN echo "DOCKER_OPTS=\"--experimental --storage-driver=vfs {{ DOCKER_EXTRA_OPTS }}\"" >> /etc/default/docker
RUN update-alternatives --set iptables /usr/sbin/iptables-legacy
# Install m2crypto package, needed by SWI tools
RUN pip3 install m2crypto==0.36.0
# Install swi tools
RUN pip3 install git+https://github.com/aristanetworks/swi-tools.git@bead66bf261770237f7dd21ace3774ba04a017e9
{% if CONFIGURED_ARCH != "amd64" -%}
# Install node.js for azure pipeline
RUN curl -sL https://deb.nodesource.com/setup_14.x | bash -
RUN apt-get install -y nodejs
# Tell azure pipeline to use node.js in the docker
LABEL "com.azure.dev.pipelines.agent.handler.node.path"="/usr/bin/node"
{% endif -%}
[PINS] Build P4RT container for PINS (#9083) - Add INCLUDE_PINS to config to enable/disable container - Add Docker files and supporting resources - Add sonic-pins submodule and associated make files Submission containing materials of a third party: Copyright Google LLC; Licensed under Apache 2.0 #### Why I did it Adds P4RT container to SONiC for PINS The P4RT app is covered by this HLD: https://github.com/pins/SONiC/blob/master/doc/pins/p4rt_app_hld.md #### How I did it Followed the pattern and templates used for other SONiC applications #### How to verify it Build SONiC with INCLUDE_P4RT set to "y". Verify that the resulting build has a container called "p4rt" running. You can verify that the service is up by running the following command on the SONiC switch: ```bash sudo netstat -lpnt | grep p4rt ``` You should see the service listening on TCP port 9559. #### Which release branch to backport (provide reason below if selected) None #### Description for the changelog Build P4RT container for PINS
2021-12-07 13:11:25 -06:00
# Install Bazel build system (amd64 and arm64 architectures are supported using this method)
# TODO(PINS): Remove once pre-build Bazel binaries are available for armhf (armv7l)
{%- if CONFIGURED_ARCH == "amd64" or CONFIGURED_ARCH == "arm64" %}
ARG bazelisk_url=https://github.com/bazelbuild/bazelisk/releases/latest/download/bazelisk-linux-{{ CONFIGURED_ARCH }}
RUN curl -fsSL -o /usr/local/bin/bazel ${bazelisk_url} && chmod 755 /usr/local/bin/bazel
# Bazel requires "python"
# TODO(PINS): remove when Bazel is okay with "python3" binary name
RUN apt install -y python-is-python3
{% endif -%}
Reference in New Issue Copy Permalink