Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion install.sh
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ SCRIPT
$SUDO sh <<SCRIPT
export DEBIAN_FRONTEND=noninteractive
mkdir -p /usr/share/keyrings/
curl -L $RELEASE_KEY | gpg --dearmor > /usr/share/keyrings/fluentbit-keyring.gpg
curl $RELEASE_KEY | gpg --dearmor > /usr/share/keyrings/fluentbit-keyring.gpg
cat > /etc/apt/sources.list.d/fluent-bit.list <<EOF
Comment on lines 136 to 140

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore redirect handling when fetching Debian key

The Ubuntu/Debian branch now calls curl $RELEASE_KEY | gpg --dearmor without -L. When the key endpoint responds with a 301/302 (common when the CDN rotates or when HTTP→HTTPS redirection is enforced), curl will not follow the redirect and instead output the redirect body. gpg --dearmor will fail, leaving an invalid keyring file and causing apt-get update to error. The earlier change you reverted was added to fix exactly this redirect scenario; dropping -L reintroduces the installation failure for any environment where the key URL redirects.

Useful? React with 👍 / 👎.

deb [signed-by=/usr/share/keyrings/fluentbit-keyring.gpg] $RELEASE_URL/${OS}/${CODENAME} ${CODENAME} main
EOF
Expand Down
Loading