Skip to content
New issue

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

OCI runtime create failed: container_linux.go:349 #1020

Closed
jwheat opened this issue Apr 27, 2020 · 8 comments
Closed

OCI runtime create failed: container_linux.go:349 #1020

jwheat opened this issue Apr 27, 2020 · 8 comments
Assignees
Labels

Comments

@jwheat
Copy link

jwheat commented Apr 27, 2020

I'm having a difficult time getting this to start. It most likely isn't a bug and has to do with something on my end, but I'm not certain what that is and was wondering if you may have an idea. I've googled quite a bit and nothing seems to work. Most 'solutions' reference permissions, but when I look, my user has full permissions over everything including the local-store directory. Maybe this just can't run with the setup I have.

Environment

I'd like to mention I am running the Ubuntu "app" on Windows 10. I have Docker for Windows running with this option checked : Expose daemon on tcp://localhost:2375 without TLS in the General settings. I also have DOCKER_HOST=localhost:2375 set in my Ubuntu terminal. Those two options allow the Ubuntu terminal to use Docker for Windows as the server. [Side note I run other RASA docker containers from the terminal so I'm fairly certain docker works]

Steps / Issue

I downloaded the .zip (0.31.1) and unzipped it in my Ubuntu terminal.
I ran docker-compose up and it went on it way pulling images.

Then it stops and I get a handful of errors like this (complete dump is further below)

 Cannot start service XXXX : OCI runtime create failed: container_linux.go:349

I did see this issue #928 (comment) before I posted and tried adding an .env like this to my directory

COMPOSE_CONVERT_WINDOWS_PATHS=1
DOCKER_HOST=localhost:2375

but get the same errors.

FWIW, I added the DOCKER_HOST line in there so I could also try the recommended sudo docker-compose up mentioned in the Basic Installation steps. Unfortunately I continue to get the same errors.

General Questions

  • Did you download a release or pull from Master? Which release?
    v0.31.1
  • What operating system are you running?
    Windows 10 with the Ubuntu terminal (app)
  • Are you running locally or in the cloud?
    Locally
  • Which browser are you using?
    Haven't gotten that far yet

Here is the console dump if that helps any.

Starting articulate-v0311_nginx_1 ...
Starting articulate-v0311_elasticsearch_1 ...
articulate-v0311_ui_1 is up-to-date
articulate-v0311_redis_1 is up-to-date
articulate-v0311_api_1 is up-to-date
Starting articulate-v0311_filebeat_1      ...
Starting articulate-v0311_filebeat_1      ... error                                                                                                                              
ERROR: for articulate-v0311_filebeat_1  Cannot start service filebeat: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449Starting articulate-v0311_rasa_1          ... error                                                                                                                              verlay2/a7b3bf19583a77f69e16b2d80357a0e896704c759152fd61b66a3c237584ad0c/merged\\\" at \\\"/var/lib/docker/overlay2/a7b3bf19583a77f69e16b2d80357a0e896704c759152fd61b66a3c237584ad0c/merged/usr/share/filebeat/filebeat.yml\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for articulate-v0311_rasa_1  Cannot start service rasa: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/rasa/rasa-config.yml\\\" to rootfs \\\"/var/lib/docker/overlay2/d09ad9200d02bfee588853c516b7e6c906f8d9f2846bc7da9c3d35ec98802c1a/merged\\\" at \\\"/var/lib/docker/overlay2/d09ad9200d02bfee588853c516b7e6c906f8d9f2846bc7da9c3d35ec98802c1a/mergeStarting articulate-v0311_elasticsearch_1 ... error                                                                                                                              the expected type

ERROR: for articulate-v0311_elasticsearch_1  Cannot start service elasticsearch: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/elasticsearch/config/elasticsearch.yml\\\" to rStarting articulate-v0311_nginx_1         ... error                                                                                                                              80e0c31e5918abd224cc25063bbc5c/merged/usr/share/elasticsearch/config/elasticsearch.yml\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for articulate-v0311_nginx_1  Cannot start service nginx: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/nginx/nginx-http.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/faf41b0836c07c7687c3acd9f66e4fe08758c09c086c8f53b0fbd1352e855b29/merged\\\" at \\\"/var/lib/docker/overlay2/faf41b0836c07c7687c3acd9f66e4fe08758c09c086c8f53b0fbd1352e855b29/merged/etc/nginx/nginx.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for filebeat  Cannot start service filebeat: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/filebeat/filebeat.yml\\\" to rootfs \\\"/var/lib/docker/overlay2/a7b3bf19583a77f69e16b2d80357a0e896704c759152fd61b66a3c237584ad0c/merged\\\" at \\\"/var/lib/docker/overlay2/a7b3bf19583a77f69e16b2d80357a0e896704c759152fd61b66a3c237584ad0c/merged/usr/share/filebeat/filebeat.yml\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for rasa  Cannot start service rasa: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/rasa/rasa-config.yml\\\" to rootfs \\\"/var/lib/docker/overlay2/d09ad9200d02bfee588853c516b7e6c906f8d9f2846bc7da9c3d35ec98802c1a/merged\\\" at \\\"/var/lib/docker/overlay2/d09ad9200d02bfee588853c516b7e6c906f8d9f2846bc7da9c3d35ec98802c1a/merged/app/config.yml\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for elasticsearch  Cannot start service elasticsearch: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/elasticsearch/config/elasticsearch.yml\\\" to rootfs \\\"/var/lib/docker/overlay2/dfba684b07abc089a44a9f7e81229d96e880e0c31e5918abd224cc25063bbc5c/merged\\\" at \\\"/var/lib/docker/overlay2/dfba684b07abc089a44a9f7e81229d96e880e0c31e5918abd224cc25063bbc5c/merged/usr/share/elasticsearch/config/elasticsearch.yml\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for nginx  Cannot start service nginx: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/mnt/d/Code/Playground/RASA/articulate-v0.31.1/local-storage/nginx/nginx-http.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/faf41b0836c07c7687c3acd9f66e4fe08758c09c086c8f53b0fbd1352e855b29/merged\\\" at \\\"/var/lib/docker/overlay2/faf41b0836c07c7687c3acd9f66e4fe08758c09c086c8f53b0fbd1352e855b29/merged/etc/nginx/nginx.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.```
@wrathagom
Copy link
Contributor

Is Docker running in Ubuntu (windows subsystem for linux) or is it Docker for Windows?

@wrathagom wrathagom self-assigned this Apr 27, 2020
@jwheat
Copy link
Author

jwheat commented Apr 27, 2020

I'm running Docker for Windows, and it is exposed to Ubuntu (WSL) where I'm executing the docker-compose up command

@wrathagom
Copy link
Contributor

Is your docker set to windows or Linux containers?

@jwheat
Copy link
Author

jwheat commented Apr 28, 2020

I was pretty sure, but just verified it is using Linux containers

@wrathagom
Copy link
Contributor

So, it looks like the source of your problem is the file mounts. Which honestly given that your in Ubuntu, but controlling the windows docker... I have no clue how you want it set.

Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

There's quite a few links to track down linked to this issue, maybe one of them can help you: docker/compose#4852

@jwheat
Copy link
Author

jwheat commented Apr 28, 2020

Ok, thanks for the pointers, I know it's an odd setup, unfortunatley I'm stuck with Windows. Maybe I'll try to do it all from there instead of in WSL. I appreciate your time. I'll play around and post back if I figure something out.

@wrathagom
Copy link
Contributor

It may be worth just trying direct from powershell. I know if works on Windows 10 because I can test that config. Just the added WSL is something I have not tested before.

@jwheat
Copy link
Author

jwheat commented Apr 28, 2020

I ran docker-compose up from powershell and it came right up, go figure, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants