Re: docker-compose issue 0.0.0.0:7051 failed: port is already allocated'
Hi,
Yes, I am on macOS,
Running this command sudo lsof -i -P -n |grep 7051 gives the following results:
Best regards,
Alexander Dedishchev
Looks like you are on macOS. Can you try running
sudo lsof -i -P -n |grep 7051
Will show if anything is listening on 7051
-----------------------------------------
Gari Singh
Distinguished Engineer, CTO - IBM Blockchain
IBM Middleware
550 King St
Littleton, MA 01460
Cell: 978-846-7499
garis@...
-----------------------------------------
-----fabric@... wrote: -----
To: Gari Singh <garis@...>
From: "Aleksandr Dedishchev"
Sent by: fabric@...
Date: 06/30/2019 07:48AM
Cc: Anil Singh <anil.singh@...>, "fabric@..." <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] docker-compose issue 0.0.0.0:7051 failed: port is already allocated'
Hi Gari, thanks!
Please, find attached docker-compose-base.yaml
Best regards,
Alexander Dedishchev
On 30/06/2019, 14:18, "Gari Singh" <garis@...> wrote:
Can you also attach base/docker-compose-base.yaml ?
-----------------------------------------
Gari Singh
Distinguished Engineer, CTO - IBM Blockchain
IBM Middleware
550 King St
Littleton, MA 01460
Cell: 978-846-7499
garis@...
-----------------------------------------
-----fabric@... wrote: -----
To: Anil Singh <anil.singh@...>, "fabric@..." <fabric@...>
From: "Aleksandr Dedishchev"
Sent by: fabric@...
Date: 06/30/2019 07:00AM
Subject: [EXTERNAL] Re: [Hyperledger Fabric] docker-compose issue 0.0.0.0:7051 failed: port is already allocated'
Dear Anil,
Thank you for e-mail and help. Please, find attached docker-compose-cli.yaml file
Please cross check you haven't mapped 7051 to any other container.
As I see from the screenshot above there is no mapping of the 7051 port to any other container.
I also do not understand santance below that no organization name matching: Org1MSP
Best regards,
Alexander Dedishchev
From: Anil Singh <anil.singh@...>
Date: Friday, 28 June 2019 at 12:20
To: Дедищев Александр Владимирович <dedishchev-av@...>, "fabric@..." <fabric@...>
Subject: Re: [Hyperledger Fabric] docker-compose issue 0.0.0.0:7051 failed: port is already allocated'
Could you please provide your docker-compose-cli.yaml file ?
Please cross check you haven't mapped 7051 to any other container.
Tanks,
Anil
On June 27, 2019 at 7:40 PM dedishchev-av@... wrote:
Dear Colleagues,
I need help. For quite some time I can not solve issue with starting network with the command
1. docker-compose -f docker-compose-cli.yaml up - d
After starting the command I get an ERROR 0.0.0.0:7051 failed: port is already allocated'
2. After executing commands docker stop $(docker ps -a -q) and killing processes running under ports I launch docker container ls and get the following in the terminal:
Alexanders-MacBook-Pro:first-network alexd$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Alexanders-MacBook-Pro:first-network alexd$ docker-compose -f docker-compose-cli.yaml up -d
3. Then I start network again and ERROR 0.0.0.0:7051 failed: port is already allocated' repeats again.
I would be very grateful for help.
--
Educational Project
Alexander
--
Educational Project
Alexander
[attachment "docker-compose-cli.yaml" removed by Gari Singh/Cambridge/IBM]
--
Educational Project
Alexander
[attachment "docker-compose-base.yaml" removed by Gari Singh/Cambridge/IBM]
Re: Re: [Hyperledger Fabric] docker-compose issue 0.0.0.0:7051 failed: port is already allocated'
--
Educational Project
Alexander