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
Seems the Docker packaging is failing right now if you don't hold it properly.
This is caused by the release-docker job (https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L435) which calls build-docker.sh (https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/scripts/build-docker.sh#L69-L70.
release-docker
build-docker.sh
These depend implicitly on package-deb-x86 (https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L403-L404)
package-deb-x86
As well as package-archive-x86_64-unknown-linux-musl (https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L384-L385)
package-archive-x86_64-unknown-linux-musl
The text was updated successfully, but these errors were encountered:
I found this while looking at #2876
Sorry, something went wrong.
jamtur01
No branches or pull requests
Seems the Docker packaging is failing right now if you don't hold it properly.
This is caused by the
release-docker
job (https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L435) which callsbuild-docker.sh
(https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/scripts/build-docker.sh#L69-L70.These depend implicitly on
package-deb-x86
(https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L403-L404)As well as
package-archive-x86_64-unknown-linux-musl
(https://github.com/timberio/vector/blob/75b89d490c17f9985089237111e83e4e8c5f71df/Makefile#L384-L385)The text was updated successfully, but these errors were encountered: