fix libssl

[patricklee2]

download and install libssl1.0.2

[leonmojica]

Hello,

I have been experiencing some issues with a couple of websites and it seems that after this change my deployment looks successful from the console but the container fails to start with the error pasted below. Is there something else around this fix that we need to do? any further help will be appreciated.

-Luis.

2018-10-18T05:15:23.256557681Z defaulting to command: "bundle exec rails server -e production -p 8080" 2018-10-18T05:15:43.779035491Z => Booting Puma 2018-10-18T05:15:43.779070492Z => Rails 5.1.6 application starting in production 2018-10-18T05:15:43.779079492Z => Run rails server -h for more startup options 2018-10-18T05:15:43.779228096Z Exiting 2018-10-18T05:15:43.781573651Z /tmp/bundle/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:292:in require': libssl.so.1.0.2: cannot open shared object file: No such file or directory - /tmp/bundle/gems/puma-3.11.4/lib/puma/puma_http11.so (LoadError) 2018-10-18T05:15:43.781732855Z from /tmp/bundle/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:292:inblock in require' 2018-10-18T05:15:43.781855958Z from /tmp/bundle/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:258:in load_dependency' 2018-10-18T05:15:43.781960460Z from /tmp/bundle/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:292:inrequire' 2018-10-18T05:15:43.782050163Z from /tmp/bundle/gems/puma-3.11.4/lib/puma/server.rb:15:in `<top (required)>' .............

[patricklee2]

@leonmojica Can you confirm the image that you are using? appsvc/ruby:2.3.3_1809071406 should have the fix this and I suspect you are on an older image.

[rrojas2385]

@patricklee2, when deploying a rails app following the quick start guide, using this command:

az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name --runtime "RUBY|2.3" --deployment-local-git

Is it possible for me to decide which ruby image to use, or the Ruby 2.3 stack automatically picks an older image without the fix ?

Thanks

[patricklee2]

I guess the deployment hasn't completed yet. In the mean time try --runtime "DOCKER|appsvc/ruby:latest"

[rrojas2385]

Thanks for your reply @patricklee2. Unfortunately 'DOCKER|appsvc/ruby:latest' throws an error on the azure CLI window as follows: 'DOCKER|appsvc/ruby:latest' is not supported.Please invoke 'list-runtimes' to cross check.

Do you have any idea about when the deployment is going to be completed?

According to Docker hub it was a month ago...

Just for the sake of testing I created a new app service to deploy my real app, with Ruby 2.3 and still got the error reported by @leonmojica.

Thanks

[patricklee2]

sorry that was the wrong parameter use --deployment-container-image-name

the deployments are starting today, so it should be done in 1-2 weeks

[rrojas2385]

Thanks @patricklee2, I ran the following command to create the app:

az webapp create --resource-group --plan --name --deployment-container-image-name appsvc/ruby:latest --deployment-local-git

I did not got any errors, but after trying to deploy using the loca git mechanism:

git remote add git add -A git commit -m "Initial deployment commit" git push

The image seems to not behave as the runtime "Ruby|2.3" does since I don't see the application files deployed on the app service. Accessing the wwwroot folder via SSH shows only the hostingstart.html file.

Do you think I am missing any other step, or should I simply wait for the new Ruby runtime to be deployed?

I am asking you because time is a luxury for me at this point, and it is critical to deploy our app using azure app services.

Thanks.

[patricklee2]

zip deploy wont work with a custom image. If you give me your site name, I can manually patch your webworker, but you wont be able to scale to new webworkers. Or you can make a docker image based on appsvc/ruby:latest with you code preloaded on. Or you can wait for the deployment to complete

I'll ask around to see if there is a better solution. If this is an issue with your production site, I recommend making a support ticket

[rrojas2385]

Thanks a lot for your help @patricklee2. We managed to create a custom image based on the one published here and that worked just fine!

[leonmojica]

Thank you very much @patricklee2 for your prompt response, we were able fix this issue