Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the allocated port for your containers (for target_deploy and others) #24

Open
ML-TANGO opened this issue Oct 22, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@ML-TANGO
Copy link
Owner

In TANGO, the leader container and member containers are identified by the their allocated host port number. Hence, adhering theirs allocated port is very important.

target_deploy service container use the incorrect port 8089, which is allocated to AutoNN (autonn_nk).

Currently this kind of misuse of the port hinders correct running of autonn_nk when docker-compose up -d --build command run as follows:

$ docker-compose up -d
[+] Running 8/9
 ⠿ Network tango_default                 Created
 ⠿ Container mariadb                     Started
 ⠿ Container tango-target_image_build-1  Started
 ⠿ Container tango-viz2code-1            Started
 ⠿ Container tango-autonn_nk-1           Starting
 ⠿ Container tango-postgresql-1          Started
 ⠿ Container tango-labelling-1           Started
 ⠿ Container tango-target_deploy-1       Started
 ⠿ Container tango-project_manager-1     Started
Error response from daemon: driver failed programming external connectivity on endpoint tango-autonn_nk-1 (d6e209f3c9de78c150dfaffc487c35584e49550fc9cee222484aa700e16ab1a1): Bind for 0.located
$ docker ps -a
CONTAINER ID   IMAGE                      COMMAND                  CREATED              STATUS              PORTS
d9d4506a19d7   tango_project_manager      "sh -c 'chmod 777 ./…"   About a minute ago   Up About a minute   0.0.0.0:8085->8085/tcp, :::8085->8085/tcp
b5b85e438d82   tango_labelling            "./start.sh"             About a minute ago   Up About a minute   0.0.0.0:8086->80/tcp, :::8086->80/tcp, 0.0.0.0:8095->10236/tcp, :::8095->1023
e6051d7109d6   tango_target_deploy        "sh -c 'python manag…"   About a minute ago   Up About a minute   0.0.0.0:8089->8089/tcp, :::8089->8089/tcp
ce7692a3e222   tango_autonn_nk            "sh -c 'python manag…"   About a minute ago   Created
1680ab1a8b75   tango_viz2code             "sh -c 'cd ./visuali…"   About a minute ago   Up About a minute   0.0.0.0:8091->8091/tcp, :::8091->8091/tcp
23cae3e37606   tango_target_image_build   "sh -c 'python manag…"   About a minute ago   Up About a minute   0.0.0.0:8088->8088/tcp, :::8088->8088/tcp
fefad2d64b8f   mariadb:10                 "docker-entrypoint.s…"   About a minute ago   Up About a minute   0.0.0.0:3306->3306/tcp, :::3306->3306/tcp
3d63c147cc2a   postgres:latest            "docker-entrypoint.s…"   About a minute ago   Up About a minute   5432/tcp

Please refer to the TANGO Containers Port Map.

I request to the responsible for the target_deploye service container for clean-up in the port mapping table in TANGO Containers Port Map.

  • It has vague or unclear porting mapping description
@ML-TANGO ML-TANGO added the bug Something isn't working label Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

3 participants