Hacker News Reader

Comment by danielsamuels | Hacker News Reader

Oh no, we tried switching over to it for a test project and it was basically a disaster. Something as simple as running Python tests and node tests on the same instance just didn't seem to be possible. We _really_ don't want to have to maintain our own Docker images. Their support forums are running Discourse too, so it's basically impossible to find anything you're looking for.

View on HN

I always found Discourse sites to be quite easy to navigate. Do you suggest anything better?

Unfortunately not. I spent many years on Proboards / VBulletin and their ilk, I don't feel like any of them really nailed it.

The problem with any community forum support is that without representatives from the company constantly on there, a question might:

- go unanswered

- get answered by the community with "here is how you do it," without the "here is why" part.

- the question can't be answered by the community and all you see are messages along the lines of "same issue here."

Rarely do I see the "here is how you do it and here is why" answer I am looking for.

Those are all valid, but none of those are inherent with Discourse, so not sure why the guy mentioned brought it up.

You don't have to maintain your own Docker image if you don't want to, though that's probably the best route for the fastest, most efficient build.

You can choose a base image (or machine, a VM), and then go from there. No custom Docker image.

Also, what's wrong with Discourse? It's not perfect but surely the best forum system around I think.

Aside from CircleCI Discuss, we also have actual Support and Docs.

we were kind of in the same boat, but realized you can still use the "machine VM" setup from before and just install the required dependencies.

Not great, but works.

You can also start with a base Docker image and then install any extra dependencies. Should be faster than the machine VM.

I don't know how possible this actually is. I was having some issues with this, personally

Like isn't the point of docker to not be able to install a bunch of stuff after the image is built?

For shipping an image yes, but that's not what you'll be doing.

For example, if you've used CircleCI 1.0 before, those builds run in LXC which is Docker's underlying technology. My suggestion is more down that path rather than 2.0's bring your own Dockerfile approach.

The base image you choose just means you don't need to install that specific language/toolset manually, which saves part of the build time and work writing the config.

Reply on news.ycombinator.com