ryan jarvinen

I'm hitting the same error with `crc start` using Fedora 36 on a ThinkPad with 64GB of RAM

Here is a copy of my `crc start --log-level debug` output from `crc-2-7-1`: https://gist.github.com/ryanj/f513967816196d36cf94b4164c2f1748 ^ This is on a 64GB laptop with `32000` memory and 8 cpus allocated in the...

This definitely looks like a bug to me: https://github.com/sclorg/s2i-nodejs-container/blob/master/14/s2i/bin/assemble#L89 `if [ "$NODE_ENV" != "production" ]; then` your NODE_ENV settings end up getting overwritten with "development"

This doesn't entirely address the issue, but you should be able to run any script that is defined in your `package.json` using the `NPM_RUN` env var. Last I checked, I...

Feel free to close this if it's not a priority. It's definitely not urgent in the short term

Try using the `PORT` env var. You should be able to set `PORT=3000`

Thanks @dharmit I'll see if I can test the new build I forgot to mention that `kubectl` and `oc` both avoid making any other writes when the `--dry-run` flag is...

Any updates on this? It's needed to support our default nodejs example app

I've tried using `--port 8080`, and I've tried the alternative, moving the app to :3000 via `--env PORT=3000`. Both options (`--port` and `--env`) don't seem to get reflected in the...

Thanks @dharmit, @serenamarie125 This works for me in interactive mode with v3.0.0beta2 Looking forward to a non-interactive way to generate a devfile as well - which might also resolve #4435