hi guys, I am getting this error when I try to run

docker/sdk bootstrap

for the first time File “./deploy.yml” is not accessible. what should I do?

Where is the screenshot? 🙂

😄

Not that small... 😄

I am running it on mac

Is deploy.yml file there? 🙂

nope ..

I can't recall a single problem if the file is there and you run docker/sdk from project's root.

but this is the first time I am running it

Without arguments bootstrap is trying to use deploy.yml.

I thought I just need to run the command

Don't think so.

how can I start it then?

If the project previously didn't have a deploy file and you used vagrant as dev env, please look at the https://github.com/spryker-shop/b2c-demo-shop/blob/master/deploy.dev.yml as an example.

I am working on b2b is it different?

Not really. https://github.com/spryker-shop/b2b-demo-shop/blob/master/deploy.dev.yml

ok thanks

Can you share more context please? 🙂 Is it an old project that was developed via vagrant devvm? And now you would like to switch to docker/sdk one?

so we have an old project developed on Vagrant … recently we upgraded Spryker to 202009,

We had a migration guide once. Let me try to find it.

that would be great

You can disable docker compose v2. Open docker preferences and you should see “disable docker compose v2” or something similar

thanks I will try this

Yep, there is a checkbox in the Docker Desktop to use composer v2.

Thank you very much I will look at it

@acoustic-businessperson-27970 make sure that you gave Docker enough resources to start all containers.

I cannot give 14GB Ram!! hahah

well, you don’t need so much, but as much as you can

btw I dont see a container for elastic search .. which one is it?

it is probably not running because it couldn’t start. Try giving docker more resources, restart the daemon and try docker/sdk up again

but in this case it should show an error?

Do you have it defined in the deploy file like https://github.com/spryker-shop/b2c-demo-shop/blob/master/deploy.dev.yml#L173?

I copied the docker.dev.yaml as is without change from b2b demo shop code

docker/sdk cli

and there you will be able to run any console commands. But workflows are a bit different in docker env. For example you can just "reset" demo data by running

docker/sdk demo

. Or build the project after you checked out other branch by running

docker/sdk build

. Or reset the project completely (like vendor/bin/install) by running

docker/sdk reset

.

hmm thanks

This sounds like ES version mismatch. For example you have ES v7 defined in the deploy file but project's modules support only ES v6.

good then I have to change my docker.dev.yml to list es version 6 instead of 7

elastic search in my project is 6.6 I set the search service to use 6.8 Now I am getting this error

Elastica\Exception\ResponseException - Exception: [include_in_all] is not allowed for indices created on or after version 6.0.0 as [_all] is deprecated. As a replacement, you can use an [copy_to] on mapping fields to create your own catch all field. [reason: Failed to parse mapping [page]: [include_in_all] is not allowed for indices created on or after version 6.0.0 as [_all] is deprecated. As a replacement, you can use an [copy_to] on mapping fields to create your own catch all field.]

The command is

vendor/bin/console search:setup:sources

Some internal feedback:

Regarding <https://docs.spryker.com/docs/scos/dev/back-end-development/data-manipulation/data-interaction/search/configuring-elasticsearch.html#defining-new-indexes-and-mappings> it looks like call updates mapping <https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html>

Mapping and (or) indexes are for old EL version needs to be updated.

But it’s not an answer on his question, I don’t know how old project was, let it be one year old.

We are using spryker/install module to init project (command vendor/bin/install, the module uses project’s install config at config/install.
One year old .yml files contain such EL related commands:
vendor/bin/console search:setup:indexes
vendor/bin/console search:setup:index-map
 Will assume that's the answer :)

so I found out that my ES is v5.6 so I changed the service definition to use 5.6 but now search container is not starting 😞

Please do

docker system prune -a && docker system prune --volumes

. Volumes for different ES versions are not compatible.

thanks I did that 😄 and it could start the search container 🎉