ddev-webserver container build fails because of unavailable packages.blackfire.io debian repo

[syssi]

Is there an existing issue for this?

• I have searched the existing issues

Output of ddev debug test

Expand `ddev debug test` diagnostic information

Skipped.

Expected Behavior

Successful container build. ddev start returns 0.

Actual Behavior

#13 [web 4/6] RUN apt-get -qq update && DEBIAN_FRONTEND=noninteractive apt-get -qq install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests webp
#13 2.896 E: Failed to fetch http://packages.blackfire.io/debian/dists/any/InRelease  403  Forbidden [IP: 3.5.66.150 80]
#13 2.896 E: The repository 'http://packages.blackfire.io/debian any InRelease' is not signed.
#13 ERROR: process "/bin/bash -c apt-get -qq update && DEBIAN_FRONTEND=noninteractive apt-get -qq install -y -o Dpkg::Options::=\"--force-confold\" --no-install-recommends --no-install-suggests webp" did not complete successfully: exit code: 100
------
 > [web 4/6] RUN apt-get -qq update && DEBIAN_FRONTEND=noninteractive apt-get -qq install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests webp:
2.896 E: Failed to fetch http://packages.blackfire.io/debian/dists/any/InRelease  403  Forbidden [IP: 3.5.66.150 80]
2.896 E: The repository 'http://packages.blackfire.io/debian any InRelease' is not signed.
------

Steps To Reproduce

ddev config --docroot=. --project-type=php --webimage-extra-packages webp && ddev start

Anything else?

Is there a workaround to get rid of blackfire.io temporary? We are dependent on the custom container build but we don't need blackfire.io usually.

[mattvb91]

same issue here. Cant even downgrade either because other versions broken too with ComposeCmd failed to run issues. Completely broken now across multiple versions.

[nostadt]

Would love to be able to disable blackfire when not needed, or actually have it disabled by default and enable if needed. Given the price of blackfire, I assume many people don't use this.

[tyler36]

Don't use it personally, but sounds like it should be extracted as an addon.

[pbowyer]

Seems to be resolved for me. Approx 1.25h after I first encountered it. Thanks Blackfire team for sorting the outage!

Edit: spoke too soon 😂 First project built; second erroring with the Blackfire outage

[fabianderijk]

It worked for me as well. Until I started another project.....

[rfay]

Could you please see if changing to nodejs_version: 18 is a workaround?

[fabianderijk]

Could you please see if changing to nodejs_version: 18 is a workaround?

That doesn't work for me

[pbowyer]

@rfay Commenting out webimage_extra_packages: [php7.4-imap] fixed it for me

[syssi]

If the ddev-webserver isn't customized using webimage_extra_packages or web-build/Dockerfile the failing apt-get update can be avoided. The custom docker image build is required in most of our projects unfortunately.

[rfay]

That was the other thing I was going to suggest, thx

[matthiaz]

Hi

There was an issue with blackfire packagecloud, a fix has been rolled out this should be resolved within a few minutes.

[rfay]

The blackfire people say this is being worked on and should be solved soon, like a few minutes.

[matthiaz]

Hi all,

I've just confirmed that the fix has been rolled out, and is working.
Please try again. Feel free to post back if you are still having issues. I'm monitoring this thread for the time being.

Matthias
Blackfire/PlatformSh team

[syssi]

It's working reliable again:

# proof
ddev stop; rm -rf .ddev; ddev config --docroot=. --project-type=php --webimage-extra-packages webp --nodejs-version 18 && ddev start; echo $?