Skip to content

Improvement: Port conflict of traffic_ops container with Kubernetes #7404

Open
@jammutkarsh

Description

@jammutkarsh

This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:

  • Dev

Current behavior:

If Kubernetes is enabled on the system and a development environment is started from dev/ using atc start. There is a port conflict between traffic_ops container and Docker backend API.

Terminal output:

$ atc start                                                                                                       

[+] Building 4.2s (45/45) FINISHED
# ----Rest of the build and start process by docker----
 ⠿ Container trafficcontrol-db-1          Running                                                                       0.0s
 ⠏ Container trafficcontrol-trafficops-1  Starting                                                                     15.9s
Error response from daemon: driver failed programming external connectivity on endpoint trafficcontrol-trafficops-1 (b09986bf574a9ce0b85b3710d1df3274bb023cdc4300aafecde215a6bc261eca): listen tcp4 0.0.0.0:6443: bind: address already in use

$ lsof -i :6443
COMMAND    PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
com.docke 8172  utc  168u  IPv4 0x264940a1a6d323cd      0t0  TCP localhost:sun-sr-https (LISTEN)

$ ps 8172
  PID   TT  STAT      TIME COMMAND
 8172   ??  S      7:07.94 /Applications/Docker.app/Contents/MacOS/com.docker.backend -watchdog -native-api

$

ref: Docker Blog

New behavior:

Change the port of Traffic_ops container.

Steps to reproduce:

  1. Start Kubernetes from Docker preferences/settings
  2. cd dev/
  3. source $(pwd)/atc.dev.sh
  4. atc start

Metadata

Metadata

Assignees

No one assigned

    Labels

    cdn-in-a-boxrelated to the Docker-based CDN-in-a-Box systemdev-ciabRelated to CDN in a Box for DevelopersimprovementThe functionality exists but it could be improved in some way.low difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break one

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions