vue-storefront-api icon indicating copy to clipboard operation
vue-storefront-api copied to clipboard

Issue with getting started following readme

Open Ju66ernaut opened this issue 7 years ago • 9 comments

I am trying to work through the readme to get the API up and running.

In the Installation section I am using the command shown for the Standard (B) mode. I checked my containers with docker container ls --all and I see the kibana, es1 and redis containers all running but the vue-storefront-api_app_1 has exited recently (like a few seconds ago).

When I try to import the product catalog after yarn restore I use the docker exec -it vuestorefrontapi_app_1 yarn restore command but I get an error "no such container" I think that is because of a typo in the readme. So I tried the same command but with vue-storefront-api_app_1 but I get a different error saying that container is not running.

I am new to docker but from what I understand it means the container ran and exited and docker exec only works on running containers. I tried to start the container again with docker start and docker run but it always exits right away.

I also tried running docker start - vue-storefront-api_app_1 but I get standard_init_linux.go:207: exec user process caused "no such file or directory" I have the vue-storefront-api directory in my docker folder...

How do I go about addressing this issue?

Running Windows 10, docker (18.09.1) and using linux containers (I tried switching to Windows containers as well but I couldn't get I got errors when running docker-compose -f docker-compose.yml -f docker-compose.nodejs.yml up -d so I switched back to linux containers)

Ju66ernaut avatar Feb 13 '19 18:02 Ju66ernaut

@Ju66ernaut The easiest way to run Vue Storefront middleware stack is to use docker-compose -f docker-compose.yml -f docker-compose.nodejs.yml up. Please run that command and post details of errors you're facing.

lukeromanowicz avatar Apr 03 '19 07:04 lukeromanowicz

Closing due to OP inactivity.

lukeromanowicz avatar Apr 23 '19 06:04 lukeromanowicz

This is the error which I'm getting while trying to install vue storefront api

$ docker-compose -f docker-compose.yml -f docker-compose.nodejs.yml up vue-storefront-api_redis_1 is up-to-date Starting elasticsearch ... error

ERROR: for elasticsearch Cannot start service es1: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused "rootfs_linux.go:58: mounting \"/f/PROJECTS/vue/vue-storefront-api/docker/elasticsearch/config/elasticsearch.yml\" to rootfs \"/mnt/sda1/var/lib/docker/overlay2/663a27dca9bd58caca70f021aff7e5b0f83cfc0c966de0c9280cd5a7268b823c/merged\" at \"/mnt/sda1/var/lib/docker/overlay2/663a27dca9bd58caca70f021aff7e5b0f83cfc0c966de0c9280cd5a7268b823c/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 es1 Cannot start service es1: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused "rootfs_linux.go:58: mounting \"/f/PROJECTS/vue/vue-storefront-api/docker/elasticsearch/config/elasticsearch.yml\" to rootfs \"/mnt/sda1/var/lib/docker/overlay2/663a27dca9bd58caca70f021aff7e5b0f83cfc0c966de0c9280cd5a7268b823c/merged\" at \"/mnt/sda1/var/lib/docker/overlay2/663a27dca9bd58caca70f021aff7e5b0f83cfc0c966de0c9280cd5a7268b823c/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 Encountered errors while bringing up the project.

harishgan avatar Aug 07 '19 02:08 harishgan

Hello I also get these errors: vue-storefront-api_kibana_1, elasticsearch and vue-storefront-api_redis_1 all start fine but vue-storefront-api_app_1 simply exits again silently. If I try using docker-compose -f docker-compose.yml -f docker-compose.nodejs.yml up I get all is fine but vue-storefront-api_app_1 exited with code 127 I'm thinking this could be the problem: app_1 | /usr/local/bin/docker-entrypoint.sh: exec: line 8: vue-storefront-api.sh: not found

SolsWebdesign avatar Jun 29 '20 16:06 SolsWebdesign

I can confirm the same problem ... vue-storefront-api_app_1 container starts and immediately exits

cafesk8 avatar Oct 16 '20 22:10 cafesk8

I have the same problem error from log Attaching to vue-storefront_app_1

app_1 | /usr/local/bin/docker-entrypoint.sh: exec: line 8: vue-storefront.sh: not found

maorz555 avatar Oct 18 '20 14:10 maorz555

I have the same issue as @maorz555 - @lukeromanowicz

app_1 | /usr/local/bin/docker-entrypoint.sh: exec: line 8: vue-storefront.sh: not found

vuedocker2 vuesfdocker1

B-Griffinn avatar Nov 12 '20 05:11 B-Griffinn

我遇到了相同的问题,请问有人解决掉吗? image image

anyaoqi avatar Mar 10 '21 03:03 anyaoqi

I'm using Portainer on RancherOS to deploy, getting similar error:

Creating volume "vuestorefront_esdat1" with default driver
Creating elasticsearch
Creating vuestorefront_redis_1
Creating elasticsearch
error
ERROR: for elasticsearch
Cannot start service es1: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting "/data/compose/4/docker/elasticsearch/config/elasticsearch.yml" to rootfs "/var/lib/docker/overlay2/072817be6b93b6585551c04e4836fa82ee05eabc8ac3c4ddb3d4d1c0b6304550/merged" at "/var/lib/docker/overlay2/072817be6b93b6585551c04e4836fa82ee05eabc8ac3c4ddb3d4d1c0b6304550/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
Creating vuestorefront_redis_1
done
ERROR: for es1
Cannot start service es1: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting "/data/compose/4/docker/elasticsearch/config/elasticsearch.yml" to rootfs "/var/lib/docker/overlay2/072817be6b93b6585551c04e4836fa82ee05eabc8ac3c4ddb3d4d1c0b6304550/merged" at "/var/lib/docker/overlay2/072817be6b93b6585551c04e4836fa82ee05eabc8ac3c4ddb3d4d1c0b6304550/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
Encountered errors while bringing up the project.

tpimh avatar Jul 19 '21 06:07 tpimh