Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hi community! I am facing a strange issue when running `docker/sdk up`. I am getting the following

Options
martin
martin CTO @ VIABIRDS Technologies GmbH Spryker Solution Partner Posts: 49 🧑🏻‍🚀 - Cadet
edited July 2021 in Docker

Hi community!

I am facing a strange issue when running docker/sdk up. I am getting the following error when running the mutagen container: Unknown service "webdriver" which aborts the process

I did not change anything noticeable in my setup and I have no idea about the root cause of this issue.

I am running MacOS 11.4 with mutagen 0.12.0-beta2 and Docker Desktop 3.5.1 .

Comments

  • martin
    martin CTO @ VIABIRDS Technologies GmbH Spryker Solution Partner Posts: 49 🧑🏻‍🚀 - Cadet
    Options

    Output of docker/sdk ps

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice
    Options

    Our internal guys had such problems.

    Thx guys, updating to Big Sur and enabling this option helped me as well 🎉
    Engine: 20.10.7
    Compose: 1.29.2
    Mutagen: 0.12.0-beta3
    
  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice
    Options
    Then ./docker/sdk prune && ./docker/sdk boot deploy.dev && ./docker/sdk up
    
  • martin
    martin CTO @ VIABIRDS Technologies GmbH Spryker Solution Partner Posts: 49 🧑🏻‍🚀 - Cadet
    Options

    Thanks!

    The issue was indeed the enabled experimental compose v2 feature. Disabling the feature resolved the issue!