Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
unable to create recipe with specified versions of rails and ruby
See original GitHub issueIssue Description
Reproduction Steps:
I just tried cloning the simple rails recipe to create a recipe that would lock to version 2.4.0 or ruby and 4.2.10 of rails, but despite adding those settings like so:
when I tested the workspace it had ruby 2.4.4 and rails 5.1 - seems like the component versions are being ignored.
Codenvy version: 5.22.1
OS and version:
OSX 10.13.5
Docker version:
where should one run ‘docker version’ ?
Codenvy cli.log output: not sure where to look for this
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, that’s what I wanted to confirm. Thanks @eivantsov !
@tansaku : This issue is solved upstream. We are going to start soon the transition of codenvy.io to another infrastructure which will leverage latest version of Eclipse Che. Stay tuned 😉
@slemeur Has this been published because I just tried and the component versions are not being honored? For example, I say Rails 5.2.2.1 and Ruby 2.5.3 but I get Rails 5.0.1 and Ruby 2.4.4. Are components here the same Ruby gem names?