Hello everyone, Tried to use Spryker Docker SDK (on Mac with Docker desktop). The environment start

U013EK8RD7A

Hello everyone,

Tried to use Spryker Docker SDK (on Mac with Docker desktop). The environment started, I see containers are running. I've also added entries to hosts file. Unfortunately, when I try to visit any shop url, I only see nginx welcome page 😭.

Does anyone has any ideas what I might have missed?

Unknown

🤔 that's a new one. What urls are you visiting?

U013EK8RD7A

Zed.de.spryker.local or yves.de.spryker.local or queue.spryker.local

U013EK8RD7A

Basically any url that was added to hosts file, as a copy paste from recommendation while setting up the dev env.

Unknown

do you have any other docker setup running?

Unknown

is there anything else that might intercept the requests?

U013EK8RD7A

No, at the moment its just Spryker b2c demo

U013EK8RD7A

Gateway container logs show the output. So it seems that for some reason it does not forward the requests 🤔

Unknown

can you reach thee yves/zed/glue containers from within the gateway container?

U013EK8RD7A

Dumb question, but what is the right way to access docker containers when using spryker docker sdk?

U013EK8RD7A

Or there is no "righter" way than just plain ol' docker exec...?

U013EK8RD7A

If I try to ping any of running services say spryker_b2c_dev_yves_us_1 or any other, it works

Unknown

i would go with the plain docker commands, as you probably just did. saw a lot of people using familiar tools like rancher or so. after all the sdk is just a wrapper for docker-compose

Unknown

can you try to curl (probably not available on the gateway container?)

U013EK8RD7A

I’ve installed curl, tried to run and got,

curl <http://spryker_b2c_dev_zed_us_1>
curl: (7) Failed to connect to spryker_b2c_dev_zed_us_1 port 80: Connection refused

# also
url spryker_b2c_dev_zed_us_1:9000
curl: (56) Recv failure: Connection reset by peer

U013EK8RD7A

ping spryker_b2c_dev_zed_us_1
PING spryker_b2c_dev_zed_us_1 (172.24.0.14): 56 data bytes
64 bytes from 172.24.0.14: seq=0 ttl=64 time=1.153 ms
64 bytes from 172.24.0.14: seq=1 ttl=64 time=0.184 ms

U013EK8RD7A

what is interesting is that I don’t seem to find any relevant nginx configurations 🤔

U013EK8RD7A

so to me it looks that none of nginx configurations were generated

U013EK8RD7A

@UJN2JRU4F, do you know if there is a way to somehow rebuild nginx?

U013EK8RD7A

I rebuild everything, but still the configuration that is defined in the template is just in the template. conf.d/default.conf is really default and there are no other conf files

U013EK8RD7A

@UJN2JRU4F so I can confirm, that in gateway nginx doesn’t have any configurations, the default.conf is trully default

U013EK8RD7A

I asked my colleague to check his environment. He has an older version where rpc_server was used instead of gateway. In his setup, default.conf has proper content

U013EK8RD7A

the build process runs w/o any errors

Unknown

hm, unfortunately @ULYHPR789 is not available today

sprymiker

I assume you could have nginx running locally on the host so requests do not go into the docker

U013EK8RD7A

But they do go, gateway container logs output the access log entry every time I visit one of the addresses

sprymiker

What about the frontend container? Or it stops in the gateway?

U013EK8RD7A

Yep it stops there. As i said default.conf in gateway does not contain any configurations that are defined in the template

sprymiker

What version of docker/sdk do you use?

U013EK8RD7A

It has nginx defaults inside, I assume this is the problem

U013EK8RD7A

Latest master