I would assume Crun is straightforwardly "Container run" with a slight bit of play on Runc (which presumably means "Run container") to emphasize that it is instead, written in C.

Given that this is an internal program name and not a product name, and that it is actually a pretty descriptive name terseness aside, I really don't see how it is so bad. Even many advanced users may never see this project name, and if they do, it will probably be in the context of being the process that actually runs their containers, in which case it should be pretty obvious.

I am the author of Crun and the name was chosen to emphasize it is in C, compete with runc and still read like "container run".

In retrospect, I could have chosen a better one.

The name is quite descriptive and fits the target audience perfectly as far as I’m concerned.

I knew exactly what you were going for from nothing but the name, so I think you did a great job personally.

The name is quite memorable and the points you made are valid; so please don't change it unless you have a very good reason to.

FWIW I really liked the name and think it’s creative yet terse and easy to search.

The name is fine. Pay no attention to the bikeshedding.

I would assume that whoever wrote "crun" had fat-fingered "cron".

I don't get it. What do you think of when reading crun? See-run? See-unn? Sirrun? Is crun perhaps some kind of slur? It's not "semen", right?

krun?

I cannot believe that you are being downvoted! This comment made me literally laugh out loud!

I thought the naming was bad because OCI is currently associated with Oracle cloud - but your critique was far better!!!

How is OCI associated with Oracle cloud?

TIL, I had only heard about OCI in the meaning from the submission (which also appears to be older than Oracle's use of the label)