Mailu : when I run docker-compose, I got this error - docker

I made a fresh install of mailu and when I run docker-compose up -d I have the following message :
Starting mailu_resolver_1 ... error
ERROR: for mailu_resolver_1 Cannot start service resolver: 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: for resolver Cannot start service resolver: 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: Encountered errors while bringing up the project.
Do you know the cause of the issue ?
Thanks for your help.
Best regards,

Docker daemon has permissions problems. Check out: https://github.com/sindresorhus/guides/blob/main/docker-without-sudo.md

Related

Chaincode container getting created but not starting

Hyperledger-Fabric: v2.3.3
Peer docker image: tag 2.3.3
Error on peer logs after committing chaincode:
ERRO 036 start-could not start container: API error (400): failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "chaincode": executable file not found in $PATH: unknown
WARN 037 could not launch chaincode 'test_v1_v1:65f5b95ca7ff438e02a86aea4205bcd697a2afa0f4e37c314d3011667357fe50': error starting container: error starting container: API error (400): failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "chaincode": executable file not found in $PATH: unknown
docker ps -a shows that chaincode container status: Created.
I tried restarting peers and orderer, but same error
*Note: Comment if I should provide any specific configuration or anything to understand the problem.
The problem was that the package name in chaincode file was not "main" (I thought that we have to name it as parent directory).
So, the binary was not getting generated after the chaincode was committed. As a result when the peer was trying to launch/run chaincode container it was saying that I don't have binary/executable file to run.
After changing package name to "main" and doing packaging, installation and commit process the chaincode container started.
*NOTE: This is my understanding of the problem, please let me know if anything written above is misconception/ wrong.

Permission when run docker on Centos7

docker: Error response from daemon:
OCI runtime create failed: container_linux.go:349:
starting container process caused “process_linux.go:449:
container init caused \“write /proc/self/attr/keycreate:
permission denied\“”: unknown.
ERRO[0000] error waiting for container: context canceled
I got this error when set up Docker on Centos7. My partner find out a solution here
My solution is running this command:
sudo setenforce Permissive

OCI runtime failed container_linux:345 starting container process caused process_linux init caused rootfs_linux:58 mounting caused perm deni unknown

I'm setting up Nakama for a personal Unity3D project.
Normally it has to return to a normal command-line. Like user#vps-24-nextwab:~$
I use Docker version 18.09.7, build 2d0083d
I tried on two different VPS, with a root and non-root user.
What I type:
sudo docker run --name=db -p 26257 -p 8080 cockroachdb/cockroach start --insecure
The output is:
docker: Error response from daemon: OCI runtime create failed:
container_linux.go:345: starting container process caused
"process_linux.go:430: container init caused \"rootfs_linux.go:58:
mounting \\"proc\\" to rootfs
\\"/var/lib/docker/vfs/dir/7c1c7c17556e9d13882fb75c32952a72b3e25cfd9ce992958d6750b5e72bbc5e\\"
at \\"/proc\\" caused \\"permission denied\\"\"": unknown.

"exec failed: container_linux.go:345 starting exec failed scripts/script.sh no such file.directory found"

I am able to generate the genesis block but when i try to start the peer to peer test network by using "UP" command it gives an error that execution failed as it cannot find the file scripts/script.sh.
I already added the path of my directory in the Virtual Machine of the docker toolbox.
note: I am using docker toolbox on windows 10: home and working with hyperledger fabric.
OCI runtime exec failed: exec failed: container_linux.go:345: starting
container process caused "exec: \"scripts/script.sh\": stat
scripts/script.sh: no such file or directory": unknown
ERROR !!!! Test failed

Docker rootfs_linux.go permission denied when mounting /proc

I'm using meteor-up to deploy to docker instances inside an LXD container. When it attempts to bring up a MongoDB docker instance, it fails with the following error:
docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:368: container init caused \"rootfs_linux.go:57: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/20a621a73755db3f4030bc67bbf7ff9540bd1d63bb348d8be440d8ca63d3c922\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"".
I've tried deploying as the ubuntu user to my LXD container, and as root, and that hasn't helped. There's obviously some permissions issue here, but I don't know where to start debugging this problem.
According to https://discuss.linuxcontainers.org/t/having-trouble-using-docker/383 it sounds like you might need to set security.nesting=true. Stop the container (lxc stop deploy-container), configure nesting on (lxc config set deploy-container security.nesting true as per https://insights.ubuntu.com/2015/10/30/nested-containers-in-lxd) and lxc start deploy-container.
For Proxmox users: https://www.youtube.com/watch?v=79KiCBNbsbg
Enable Nesting feature on the container to fix the following error
ERROR: for mysql-8.0 Cannot start service mysql-8.0:
failed to create shim: 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
But other users Proxmox users say to enable keyctl too.
If you still have errors you may need to remove domain_name and hostname from the docker-compose config to fix the following errors as said here.
ERROR: for mariadb10-4 Cannot start service mariadb10-4: failed to create shim: OCI runtime create failed: container_linux.go:380:
starting container process caused: process_linux.go:545:
container init caused: write sysctl key kernel.domainname:
open /proc/sys/kernel/domainname: permission denied: unknown

Resources