Ignoring xx-yy because its extensions are not built. Try: gem pristine xx --version yy

[KonoMaxi]

I keep getting this message with my pipeline initiated deployments.

I tracked the issue down to the way the compiled extensions are stored.
I rebuilt the current master image for 2.6.2 locally and tested the behaviour of bundle --path 'vendor/bundle' for your image (appsvc/ruby:2.6.2_20200101.1) against mine (moxxxy/appsvc-ruby:2.6.2)

Please note the different folder-structure in vendor/bundle/ruby/2.6.0/extensions/x86_64-linux
My image (and my Azure build-pipelines) put the extensions into a 2.6.0 folder, while your image puts them into 2.6.0-static folder.

The rather inconvenient result of this minimal difference is a recompilation of the native extensions for all gems. This literally takes forever, exceeding the 230 second Cold-Start timeout and letting my apps crash.

Currently I can only run my apps in an "Azure Web App for Containers" environment, but if you could attend to this issue I can go back to using your provided ruby-appsvc images.

Also here's a screenshot from my appsvc test-environment showing both folders.
The timestamp 23:55 is the time my CI built the extensions.
00:01 the next day is the app service's startup.sh rebuilding those extensions

[gregogalante]

I'm getting the same problem after un update of the service from ruby 2.3 to 2.6. @KonoMaxi how did you solve this?

[KonoMaxi]

Hi @gregogalante, sadly I couldn't solve this in a desirable way.

I'm quoting feedback I got from Microsoft Support: "Webapps for containers is the way to go in your scenario, and also [product team's feedback] unfortunately confirms that they will no longer be supporting updates for the Ruby 2.6 image, as the interest for this service lags behind (most customers using Ruby on Webapps being on custom container already)."

So I keep using a custom image, thats fine(ish) - but in my opinion they should remove ruby from the list of supported languages for azure app-service.