Nick Sieger

Results 59 comments of Nick Sieger

Thanks for filing compose-spec/compose-go#310 (linking it here).

I'd say it's fine to keep the log/tmp artifacts of Rails generation. Those directories still get used during development.

Hey @kochalex, thanks for submitting this! It looks pretty good to me overall. It looks like you may have copied the readme and some boilerplate from another sample, as the...

I think trying to infer overrides by looking at files is going to be tricky without knowing how the developer wants the files to be applied. The fact that Tilt...

Ok, that setup makes sense. So what is it about Tilt's current behavior that merges multiple docker compose statements and/or files into a single project that's problematic? Is it the...

There's a new argument to `dc_resource` called `new_name` that will help with this issue. You will need to change the name of the first resource before the second `docker_compose` call...

I can't tell much from the commit history, it looks like the context commands here evolved around the same time or a little bit after those in docker/cli. Originally maybe...

I'm sorry this issue has been ignored for this long, to the point where it won't be fixed in compose v1 due to the [end-of-life policy](https://github.com/docker/roadmap/issues/257). Are you able to...

Can you try running without buildkit and see if the result is any different? ``` DOCKER_BUILDKIT=0 docker compose build nvidia-test ```

@KoditkarVedant can you please try updating your branch one more time and I'll make sure CI runs cleanly.