Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build image, 202111 branch, Error 2 #10055

Open
aussieserverhosts opened this issue Feb 22, 2022 · 4 comments
Open

Unable to build image, 202111 branch, Error 2 #10055

aussieserverhosts opened this issue Feb 22, 2022 · 4 comments
Assignees
Labels
Triaged this issue has been triaged

Comments

@aussieserverhosts
Copy link

aussieserverhosts commented Feb 22, 2022

Description

Unable to build the image, following instructions on the README.md as per:
https://github.com/Azure/sonic-buildimage

Steps to reproduce the issue:

Fresh Ubuntu 20.04 install
sudo apt install -y python3-pip
sudo pip3 install j2cli
sudo apt install docker.io
sudo gpasswd -a ${USER} docker
git clone -b 202111 https://github.com/Azure/sonic-buildimage.git
sed -i 's/INCLUDE_ICCPD = n/INCLUDE_ICCPD = y/g' sonic-buildimage/rules/config
sudo modprobe overlay
cd sonic-buildimage
make init
make configure PLATFORM=broadcom
make SONIC_BUILD_JOBS=4 all

Also attempted to build without enabling ICCPD with the same results

Describe the results you received:

Build fails with Error 2

Describe the results you expected:

Successful build

Attached build log

buildlog.log

@aussieserverhosts aussieserverhosts changed the title Unable to build image, Error 2 Unable to build image, 202111 branch, Error 2 Feb 22, 2022
@mfyuce
Copy link

mfyuce commented Feb 28, 2022

Can you provide the following logs (if they exist on the target folder) ?;

  • target/sonic-broadcom.bin.log
  • target/sonic-broadcom.bin.gz.log
  • target/docker-lldp.gz.log

or the last changed ten (10) logs in the target folder?

At first skim, it seems memory related.
Also trying with one job may resolve or give better insights; make SONIC_BUILD_JOBS=1 all

@zhangyanzhao zhangyanzhao added the Triaged this issue has been triaged label Mar 2, 2022
@zhangyanzhao
Copy link
Collaborator

@mfyuce please help and thanks.

@aussieserverhosts
Copy link
Author

Can you provide the following logs (if they exist on the target folder) ?;

  • target/sonic-broadcom.bin.log
  • target/sonic-broadcom.bin.gz.log
  • target/docker-lldp.gz.log

or the last changed ten (10) logs in the target folder?

At first skim, it seems memory related. Also trying with one job may resolve or give better insights; make SONIC_BUILD_JOBS=1 all

Tried to run it again with make SONIC_BUILD_JOBS=1 all, but there's no output this time, unfortunately I had already purged the previous logs before trying again

BLDENV=bullseye make -f Makefile.work all
make[1]: Entering directory '/home/builder/sonic-buildimage'
~/sonic-buildimage/src/sonic-build-hooks ~/sonic-buildimage
make[2]: Entering directory '/home/builder/sonic-buildimage/src/sonic-build-hooks'
dpkg-deb: building package 'sonic-build-hooks' in 'buildinfo/sonic-build-hooks_1.0_all.deb'.
make[2]: Leaving directory '/home/builder/sonic-buildimage/src/sonic-build-hooks'
~/sonic-buildimage
SONiC Build System

Build Configuration
"CONFIGURED_PLATFORM"             : "broadcom"
"CONFIGURED_ARCH"                 : "amd64"
"SONIC_CONFIG_PRINT_DEPENDENCIES" : ""
"SONIC_BUILD_JOBS"                : "1"
"SONIC_CONFIG_MAKE_JOBS"          : "20"
"SONIC_USE_DOCKER_BUILDKIT"       : ""
"USERNAME"                        : "admin"
"PASSWORD"                        : "YourPaSsWoRd"
"ENABLE_DHCP_GRAPH_SERVICE"       : ""
"SHUTDOWN_BGP_ON_START"           : ""
"ENABLE_PFCWD_ON_START"           : ""
"SONIC_BUFFER_MODEL"              : ""
"INSTALL_DEBUG_TOOLS"             : ""
"ROUTING_STACK"                   : "frr"
"FRR_USER_UID"                    : "300"
"FRR_USER_GID"                    : "300"
"ENABLE_SYNCD_RPC"                : ""
"ENABLE_ORGANIZATION_EXTENSIONS"  : "y"
"HTTP_PROXY"                      : ""
"HTTPS_PROXY"                     : ""
"NO_PROXY"                        : ""
"ENABLE_ZTP"                      : ""
"INCLUDE_PDE"                     : ""
"SONIC_DEBUGGING_ON"              : ""
"SONIC_PROFILING_ON"              : ""
"KERNEL_PROCURE_METHOD"           : "build"
"BUILD_TIMESTAMP"                 : "20220304.221933"
"BUILD_LOG_TIMESTAMP"             : "none"
"SONIC_IMAGE_VERSION"             : "202111.0-dirty-20220304.221933"
"BLDENV"                          : "bullseye"
"VS_PREPARE_MEM"                  : "yes"
"INCLUDE_MGMT_FRAMEWORK"          : "y"
"INCLUDE_ICCPD"                   : "y"
"INCLUDE_SYSTEM_TELEMETRY"        : "y"
"ENABLE_HOST_SERVICE_ON_START"    : "n"
"INCLUDE_RESTAPI"                 : "n"
"INCLUDE_SFLOW"                   : "y"
"INCLUDE_NAT"                     : "y"
"INCLUDE_DHCP_RELAY"              : "y"
"INCLUDE_P4RT"                    : "n"
"INCLUDE_KUBERNETES"              : "n"
"INCLUDE_MACSEC"                  : "y"
"INCLUDE_MUX"                     : "y"
"TELEMETRY_WRITABLE"              : ""
"ENABLE_AUTO_TECH_SUPPORT"        : "y"
"PDDF_SUPPORT"                    : "y"
"MULTIARCH_QEMU_ENVIRON"          : "n"
"SONIC_VERSION_CONTROL_COMPONENTS": "none"

"SONIC_DPKG_CACHE_METHOD"         : "none"

make: *** No rule to make target 'target/docker-database.gz', needed by 'target/sonic-broadcom.bin'.  Stop.
make[1]: *** [Makefile.work:306: all] Error 2
make[1]: Leaving directory '/home/builder/sonic-buildimage'
make: *** [Makefile:31: all] Error 2

@mfyuce
Copy link

mfyuce commented Mar 18, 2022

Thank you for the information.

Logs inside each folder in "target" could be of help. For example "debs", "python-debs" etc folders will contain such logs.

On the other hand, there is a bug in p4rt which is solved by this PR which is not integrated in the mainstream yet.

Can you cherry pick it and apply it to your codes and then try it? Then lets us know "what happens".

I say "what happens" because, that PR was for vs platform and there may be other issues related to broadcom binaries.

Other than that, what I can say is, the public relations (PR :) ) at here seems a very early presentation for now, which I am still struggling to keep p4rt binary up inside p4rt docker container. That is to say, it seems, with the merge of "pins" to SONIC, there are things to overcome for easy and smooth working with p4rt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triaged this issue has been triaged
Projects
None yet
Development

No branches or pull requests

3 participants