Tons of RESOURCE_BUSY errors on containerevent.create

I am trying to deploy a basic blog (ghost) service from the rancher catalog. It’s been stuck in ‘scheduling’ for about 15 minutes, so I checked out the ‘processes’ page, and it looks like hundreds of containerCreate commands are failing every minute with a RESOURCE_BUSY error.

I’m assuming this isn’t normal. Looking at the api entries for a few of these, they all fail with the same exception type: Failed to acquire lock [CONTAINEREVENT.INSTANCE.CREATE.28.897754092]. Is there something wrong with my cluster? Anything I can do to debug the issue?

It looks like even after cancelling the ghost deploy these errors are still logged continuously.