Problem with Ruby: ["env: './configure': Permission denied"]

[jamesbeedy]

Deploying a charm (on private infrastructure) built with layer ruby fails with -> http://paste.ubuntu.com/23539306/

This charm is being deployed on Xenial, but is on private infrastructure, which might have pre-baked restrictions on where things can be executed. Can we unpack and configure somewhere other than /tmp?

[jameinel]

I can imagine a system where /tmp is flagged with "noexec". However, where else should something like layer-ruby put its intermediate files?
As for "fails with layer-ruby", why are you using layer-ruby if you don't need it?

[jamesbeedy]

@jameinel a few reasons, 1) layer ruby exposes the 'gem' and 'bundle' functions which are a nice abstraction over using the chdir context + shelling out to bundle exec calls, 2) layer ruby gives me a standardized way to provide different apps with a pluggable ruby version and flat way to interface to installing ruby the same way in each ruby application charm.

It's not that big of a deal for me to rip it out and shell out the handful of bundle commands, it was just one of many things that broke on me today. I'll be deploying this application/charm across multiple providers for multiple clients, the same goes for the other ruby apps I have - hoping layer-ruby would dry things up to this extent.