hey docker peeps, i've been running into this erro...
# docker
a
hey docker peeps, i've been running into this error, it seems to happen when I switch projects, at first I thought it was specific to code changes but now I'm thinking it has specifically to do with switching projects. MacOS 11.2.1 / Docker Desktop / Docker version 20.10.2 / docker-compose version 1.27.4 Docker down to stop one project
Copy code
$ docker/sdk down
$ cd path/to/other/sprykerProject
At first I try this
Copy code
$ docker/sdk reset
$ docker/sdk boot deploy.dev.yml # if it's a new project I have to switch to mutagen
$ docker/sdk up
Sometimes this only seems to do it, but today... It runs until it hits the frontend build and then
Aborted install...
Copy code
$ docker/sdk down
$ docker/sdk boot deploy.dev.yml 
$ docker/sdk clean && docker/sdk clean-data
$ docker/sdk up --build --assets --data
Sometimes this also seems to work, but today... It runs until it hits the frontend build and then
Aborted install...
Copy code
$ docker/sdk down
$ docker system prune -a && docker system prune --volumes # this has worked in the past for these kinds of things, maybe referencing incorrect container?
$ docker/sdk boot deploy.dev.yml 
$ docker/sdk up
This was my goto, but today i tried it and... It runs until it hits the frontend build and then
Aborted install...
Copy code
$ docker/sdk down
$ docker/sdk boot deploy.dev.yml 
$ docker/sdk clean-data && docker/sdk up && docker/sdk console q:w:s -v -s
Today this last command worked. Which is sort of answering my own question. The real question is: Is there a way to switch projects reliably every time If one wants to switch from SprykerProject1 to SprykerProject2 follow these steps...
a
In the deploy file there is
namespace
Change it for each project. This way images and volumes won't be a problem.
I have around 8-9 different projects. Stop one, change directory, start another. Simply as is.
a
alright, well all these projects have the same namespace, the error part of that, checks out 🤣 I'll give it a shot. thanks @average-branch-45579 🙏
👍 1
a
Don't forget to bootstrap after changing the namespace.
✅ 1
a
ok changing the namespaces seems to work most of the time but not all the time... this looks like a timeout error to me, like it's taking so long to build that it gets cutoff
It was working pretty well for the last couple days of last week though...
a
What was the command?
docker/sdk build
? It isn't related to namespaces IMO.
a
docker/sdk up
docker/sdk up --build --assets --data
both produce the same result, yeh I don't really know whats going on, and don't know how to debug as there isn't a lot of data yo work with, it's happened in multiple cases in different repos, but all using the docker/sdk repo...
alright I think I might have figured out what is going on... some artifacts must get left behind... hard to do a prune and then hard reset
docker/sdk trouble && rm -rf vendor && rm -rf src/Generated && docker/sdk sync && docker/sdk up
✅ 1
👍 1