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

Running multiple instances of skaffold no longer possible #1733

Closed
pre opened this issue Mar 6, 2019 · 5 comments
Closed

Running multiple instances of skaffold no longer possible #1733

pre opened this issue Mar 6, 2019 · 5 comments
Assignees
Labels
area/eventing needs-reproduction needs reproduction from the maintainers to validate the issue is truly a skaffold bug priority/p2 May take a couple of releases

Comments

@pre
Copy link

pre commented Mar 6, 2019

Expected behavior

Have two projects with A/skaffold.yml and B/skaffold.yml.

Expected: running skaffold dev in both directories A and B would work. This used to work in an earlier version still in January 2019.

Actual behavior

Running skaffold dev for project A will work as expected, but skaffold dev for project B will fail.

The error message is:

FATA[0000] creating runner: creating runner: initializing skaffold event handler: creating status server: creating listener: listen tcp :50051: bind: address already in use

Information

  • Skaffold version: fails with v0.24.0
  • Operating system: MacOS Mojave
  • Contents of skaffold.yaml: anything

Steps to reproduce the behavior

  1. Create A/skaffold.yml
  2. Create B/skaffold.yml
  3. Run skaffold dev under A
  4. Run skaffold dev under B
    -> fails with listen tcp :50051: bind: address already in use (this used to work still in January 2019)
@matti
Copy link
Contributor

matti commented Mar 6, 2019

skaffold dev --rpc-port :50052

seems to work.

@tejal29 tejal29 added priority/p2 May take a couple of releases needs-reproduction needs reproduction from the maintainers to validate the issue is truly a skaffold bug area/eventing labels Mar 6, 2019
@tejal29
Copy link
Contributor

tejal29 commented Mar 6, 2019

cc @nkubala who might have a better idea since this seems relevant to the Event API work he did.

@nkubala
Copy link
Contributor

nkubala commented Mar 6, 2019

@pre thanks for the issue. I opened a PR that will fix this, but in the meantime you can use @matti's workaround to keep running skaffold.

@tejal29
Copy link
Contributor

tejal29 commented Mar 6, 2019

@nkubala Can you point us to the workaround? is it same as using --rpc-port flag?

@nkubala
Copy link
Contributor

nkubala commented Mar 7, 2019

@tejal29 yeah specifying another rpc port fixes it. the previous logic to choose a new port if the provided/default one is already in use was busted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/eventing needs-reproduction needs reproduction from the maintainers to validate the issue is truly a skaffold bug priority/p2 May take a couple of releases
Projects
None yet
Development

No branches or pull requests

4 participants