Fails to find nodejs version about herokuish

[josegonzalez]

Other than the title, this issue has no information, so I’m not sure how I would even begin to debug this. I’m going to close this, but feel free to comment with an explanation of what you are doing, what you expect to happen, what actually happened, and a code base I can replicate your issue with.

[PauloFavero]

Other than the title, this issue has no information, so I’m not sure how I would even begin to debug this. I’m going to close this, but feel free to comment with an explanation of what you are doing, what you expect to happen, what actually happened, and a code base I can replicate your issue with.

Sorry, I miss clicked and the issue was created without a description. I already updated the issue.

Thanks

[PauloFavero]

@josegonzalez if you need further info regarding the test environment please let me know.

[josegonzalez]

Do you have a sample app I can run with? Additionally, you might want to open up a ticket with Gitlab, as this is part of their autodevops product, and I've already mentioned to them that its basically unsupported other than updating buildpacks.

[PauloFavero]

I will provide a small setup to reproduce this behavior. In parallel, I will create an issue with Gitlab.

[josegonzalez]

Maybe if you can set the --ulimit memlock=-1 docker option, that would work. We had a similar issue here in dokku.

Closing as I'm pretty sure this is going to be fixed client-side, not in this repo.