You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like it is linked to the upgrade to 1.3.x line of browsertrix base image, which include an upgrade to Ubuntu Noble. At least a good track to follow.
It is the arm64 build (which is using buildx) which takes much much longer. Lot's of person on the Internet are experiencing problems around Noble and arm64, especially when not running on native hardware. Every topics I found always ended up with something circumventing the problem. I strongly suspect there is still a problem with Ubuntu Noble on arm64.
I tried to simply build again browsertrix-browser-base with buildx and the arm64 seems to never be finishing, I will update once it is done. It wasn't the case with previous Ubuntu used which I already built with buildx.
I see three alternatives:
open an issue upstream to fix Ubuntu Noble (good luck, I have no idea where I should open the issue, suggestions more than welcomed, and it is probably going to take very long)
split build job, on per platform, so that it can run natively. But is this possible with our Github action, can we build the two plateforms Docker images in two different jobs?
drop support for arm64: do we really need this image? I do not recall why we are doing this for a scraper, most (all?) other scraper seems to build only for amd64
Since few weeks, publishing jobs for dev and release suddenly jumped from less than 10 minutes to more than 40 minutes
This is not normal and should at least be investigated, and probably fixed.
The text was updated successfully, but these errors were encountered: