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.

Sign up for GitHub

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

Jump to bottom

Use predefined port numbers for dockerized TestCafe #1728

Closed
AndreyBelym opened this issue Aug 24, 2017 · 1 comment
Closed

Use predefined port numbers for dockerized TestCafe #1728

AndreyBelym opened this issue Aug 24, 2017 · 1 comment
Assignees
@AndreyBelym
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser connection TYPE: bug The described behavior is considered as wrong (bug).
Milestone
Sprint #9

Comments

@AndreyBelym
Copy link
Contributor

AndreyBelym commented Aug 24, 2017 •
edited
Loading

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

Dockerized TestCafe doesn't use predefined 1337 and 1338 network ports. It prevents connecting remote browsers to it, because ports opened in a container must be explicitly exposed in Dockerfile or Docker CLI in order to be visible from host network: https://docs.docker.com/engine/reference/run/#expose-incoming-ports

What is the expected behavior?

TestCafe uses 1337 and 1338 ports in the container, so remote browsers can be connected from the Docker host system.

How would you reproduce the current behavior (if this is a bug)?

Run TestCafe container with browser remote.

Specify your

  • operating system: Any, Docker container
  • testcafe version: 0.17.1
  • node.js version: any
@AndreyBelym AndreyBelym added AREA: server SYSTEM: browser connection TYPE: bug The described behavior is considered as wrong (bug). labels Aug 24, 2017
@AndreyBelym AndreyBelym self-assigned this Aug 24, 2017
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #9 milestone Aug 24, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Aug 30, 2017
@AndreyBelym
Use exposed Docker ports (closes DevExpress#1728)
3920031
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
@AndreyBelym @kirovboris
Use exposed Docker ports (closes DevExpress#1728) (DevExpress#1744)
f4abdf6
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AndreyBelym AndreyBelym

Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser connection TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Milestone
Sprint #9
Development

No branches or pull requests
2 participants
@AndreyBelym @AlexanderMoskovkin