We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi @carlosvin
I am trying to run the example, but I get the following output from docker-compose up:
ERROR: for docker-reverse-proxy-multi-domain_nginx-proxy_1 Cannot start service nginx-proxy: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resultingStarting docker-reverse-proxy-multi-domain_b_1 ... done
ERROR: for nginx-proxy Cannot start service nginx-proxy: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown
This is the configuration I am trying on VPS:
docker-compose.yaml
a: build: a environment: VIRTUAL_HOST: a.criptoconversor.tech restart: always b: build: b environment: VIRTUAL_HOST: b.criptoconversor.tech restart: always nginx-proxy: image: jwilder/nginx-proxy ports: - "80:80" - "443:443" volumes: - /var/run/docker.sock:/tmp/docker.sock:ro restart: always privileged: true
/etc/hosts
127.0.0.1 a.criptoconversor.tech 127.0.0.1 b.criptoconversor.tech
Dockerfiles in a and b folder were not edited.
a
b
Any idea why this might be happening?
I get the same error in my laptop as well, using my hostname instead of the production domain name.
Thanx.
The text was updated successfully, but these errors were encountered:
Adding more info about the system from carlosvin/carlosvin.github.io#40 (comment) Failing in:
OS: Ubuntu 20.04.1 LTS Docker: Docker version 19.03.12, build 48a66213fe Compose: docker-compose version 1.25.0, build unknown
Tested on Archlinux and Mac Catalina: OK
Sorry, something went wrong.
No branches or pull requests
Hi @carlosvin
I am trying to run the example, but I get the following output from docker-compose up:
ERROR: for docker-reverse-proxy-multi-domain_nginx-proxy_1 Cannot start service nginx-proxy: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resultingStarting docker-reverse-proxy-multi-domain_b_1 ... done
ERROR: for nginx-proxy Cannot start service nginx-proxy: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown
This is the configuration I am trying on VPS:
docker-compose.yaml
/etc/hosts
Dockerfiles in
a
andb
folder were not edited.Any idea why this might be happening?
I get the same error in my laptop as well, using my hostname instead of the production domain name.
Thanx.
The text was updated successfully, but these errors were encountered: