oci runtime error after upgrading Docker on Arch Linux
By Josh Sherman
Sat down to knock out some blog posts recently and when I ran docker-compose
up to get my blog up and running locally I was faced with a pretty aggressive
What the actual fuck?!
I assumed it had something to do with the fact that I had accidentally killed
the power to my desktop machine while trying to figure out with switch on the
circuit breaker went to one of the kitchen lights that needed some love.
Also thought maybe it related to the other issues I have had recently with my
blog’s containers where the Gemfile.lock gets all stupid and has to be blown
To confirm if it was specific to my blog, I tried to bring up the containers
from another project of mine. Same deal though, so it was probably Docker
Having issues like this in the past, the first thing I tried was running
docker-compose up again as root (with sudo).
Same deal again. So I decided to check the status of Docker’s service:
Well hot damn!
I assumed that warning was the cause of the problem as I have run into it in the
past and running that command fixed things.
Thought is that I had ran an update recently but since I hadn’t needed to bounce
any containers it wasn’t a problem. The moment I killed the power and restarted
the box, the issue cropped up.
Upon running systemctl daemon-reload and then bouncing the Docker service with
systemctl restart docker, the Docker service stopped complaining and
everything was right with the world again: