We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
40.63 Errors were encountered while processing: 40.63 /tmp/apt-dpkg-install-sKgA5q/018-libgprofng0_2.40-2_amd64.deb 40.67 E: Sub-process /usr/bin/dpkg returned an error code (1) ------ Dockerfile:61 -------------------- 60 | 61 | >>> RUN --mount=type=bind,source=docker/debian_packages.txt,target=/debian_packages.txt \ 62 | >>> <<EOF 63 | >>> # Allow scripts to detect we are running in our own container 64 | >>> touch /addons-server-docker-container 65 | >>> # install packages. 66 | >>> apt-get update 67 | >>> grep -v '^#' /debian_packages.txt | xargs apt-get -y install 68 | >>> rm -rf /var/lib/apt/lists/* 69 | >>> EOF 70 | -------------------- ERROR: failed to solve: process "/bin/bash -xue -c # Allow scripts to detect we are running in our own container\ntouch /addons-server-docker-container\n# install packages.\napt-get update\ngrep -v '^#' /debian_packages.txt | xargs apt-get -y install\nrm -rf /var/lib/apt/lists/*\n" did not complete successfully: exit code: 123
The install script for debian packages sometimes fails on "dpkg".. we should have better retry, error handling of these intermittent failures.
This script should pass and ideally recover from errors with retry mechanisms as most of the time just running the build again works.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
The install script for debian packages sometimes fails on "dpkg".. we should have better retry, error handling of these intermittent failures.
What did you expect to happen?
This script should pass and ideally recover from errors with retry mechanisms as most of the time just running the build again works.
Is there an existing issue for this?
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: