Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

Local Fabric does not work with Docker Compose v1.23 #347

Closed
sstone1 opened this issue Nov 20, 2018 · 5 comments
Closed

Local Fabric does not work with Docker Compose v1.23 #347

sstone1 opened this issue Nov 20, 2018 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@sstone1
Copy link
Contributor

sstone1 commented Nov 20, 2018

Docker Compose v1.23 introduces a breaking change to container names that the extension relies upon:

The default naming scheme for containers created by Compose in this version
has changed from <project>_<service>_<index> to
<project>_<service>_<index>_<slug>, where <slug> is a randomly-generated
hexadecimal string. Please make sure to update scripts relying on the old
naming scheme accordingly before upgrading.
@sstone1 sstone1 added the bug Something isn't working label Nov 20, 2018
@sstone1 sstone1 self-assigned this Nov 20, 2018
heatherlp added a commit that referenced this issue Nov 20, 2018
Specify explicit container names instead of defaults (resolves #347)
@horeaporutiu
Copy link

Is this fixed? I still have the same problem as described in #354

@alopezmancisidor
Copy link

I have exactly same error. What version of Docker Compose can I use instead until fix is deployed? Thanks!

@horeaporutiu
Copy link

@alopezmancisidor

Update - works now.
Not sure why... didn't do anything different my computer has been acting up, so that could possibly it.

@jentityframework
Copy link

@horeaporutiu

Can you tell my version of Docker Compose you're using

@horeaporutiu
Copy link

@jentityframework

testDirApril3$ docker-compose -v
docker-compose version 1.23.2, build 1110ad01

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants