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

composer server destroy returns an error if docker proxy server is in use #279

Open
1 task
jazzsequence opened this issue Apr 5, 2021 · 0 comments
Open
1 task
Labels
bug Existing functionality isn't behaving as expected developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now

Comments

@jazzsequence
Copy link
Contributor

It may not be possible to silence this error, but it is an error that shows up when you run composer server destroy on a machine that is using other Altis local server instances.

Steps to reproduce:

  1. Create multiple Altis environments
  2. Make sure that both have run composer serve at least once each (so the containers are set up)
  3. run composer server destroy on one of the environments
  4. see error in terminal

Expected behavior:
No error displays after destroy command is run.

Screen Shot 2021-04-05 at 3 11 58 PM

Acceptance criteria:

  • ...
@jazzsequence jazzsequence added the bug Existing functionality isn't behaving as expected label Apr 5, 2021
@PriyaBhatia0210 PriyaBhatia0210 added could have Could be done, or nice to have, low priority for now should have Should be done, medium priority for now and removed could have Could be done, or nice to have, low priority for now labels Apr 13, 2021
@yumito yumito removed the cross-team label Nov 23, 2021
@missjwo missjwo added the developer advocacy Developer Advocacy related tasks label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Existing functionality isn't behaving as expected developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

4 participants