Error on quickstart.sh (Ubuntu 18.04.5 LTS)

[TatLead]

I got this error after entering the data on ./quickstart.sh with test mode 🤔

OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown

OS Version

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.5 LTS
Release:        18.04
Codename:       bionic

Docker Version

Docker version 20.10.10, build b485636

Docker Compose Version

docker-compose version 1.23.2, build 1110ad01

Full Log

     RUNNING IN TEST MODE
The various docker containers will now be built.

You will see large amount of console output you may or may not recognize. Please let the script run uninterrupted.
It may take several minutes to complete.

Building refractor-frontend
Step 1/13 : FROM node:15-alpine AS build
 ---> 75631da67663
Step 2/13 : RUN apk --no-cache add git
 ---> Running in fcfb834f700b
ERROR: Service 'refractor-frontend' failed to build: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown
Starting nginx...
Building refractor
Step 1/24 : FROM golang:alpine AS build
 ---> cfd0f4793b46
Step 2/24 : RUN apk --no-cache add gcc g++ make git
 ---> Running in 999936a3afe9
ERROR: Service 'refractor' failed to build: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown
Deleting dummy certificate for panel.dukeofyork.org...
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown


Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown

ERROR: No containers to restart
If you received a message from nginx mentioning an unknown or disconnected host refractor, something prevented the backend from starting.
You should run docker logs refractor to see what the issue is.
Once the issue was fixed and the backend is functioning normally, you must restart the proxy using docker restart nginx

If you didn't get any errors, then you're all set!

Enjoy Refractor!

[Duncan]

Hey there, thanks for reporting this.

A few things to check:

1. Are you running this container inside another container (nesting)?

2. Could you try to build just the refractor-frontend service alone just to ensure it's not a conflict with other containers? This is likely not the issue, but it doesn't hurt to check. The following command should work:

docker-compose -f docker-compose.yml -f compose-frontend-svelte.yml up -d --force-recreate --build --no-deps refractor-frontend

3. If you get the same error, please provide your current containerd version. containerd --version and consider upgrading docker-compose to the latest version.

4. Please confirm whether or not you're able to build/run any docker container on your system.

[TatLead]

You are right, even Hello world not working... 😨

sudo docker run hello-world
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: permission denied: unknown.
ERRO[0000] error waiting for container: context canceled

I googled many times still no solution...

If anyone has some ideas please feel free to comment below.

[Duncan]

@BattlefieldDuck What kind of machine are you hosting on? VPS or Dedi?

Also, have you tried doing a full uninstall and reinstall of docker and compose? I'd suggest following the two links below since you're using Ubuntu.

Install Docker Engine and
Install Docker Compose under the linux tab.

If I had to guess, your containerd or docker installation might be either lacking permission or be configured incorrectly. Reinstalling docker and it's dependencies will hopefully resolve that.

Please let me know how it goes!

[TatLead]

It should be docker problem on specific VPS, I tried on another two VPS doesn't encounter this problem.