SeleniumHQ / SeleniumHQ/docker-selenium

[🐛 Bug]: Can't connect to VNC when deployed on Azure Container

Open
#2,295 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

R-awaiting-answer
Dominant language
Go
Stars
8.7k
Forks
2.5k
Avg merge
10h 16m
Merged PRs (30d)
20

Description

What happened?

Hi, i deployed a container based on the selenium/chrome_standalone. It works everything except the connection to VNC.
Seems that the port it's not exposed, did i missed anything?

Thanks for the help

Command used to start Selenium Grid with Docker (or Kubernetes)
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "containerGroups_selenium_search_app_name": {
            "defaultValue": "selenium-search-app",
            "type": "String"
        }
    },
    "variables": {},
    "resources": [
        {
            "type": "Microsoft.ContainerInstance/containerGroups",
            "apiVersion": "2023-05-01",
            "name": "[parameters('containerGroups_selenium_search_app_name')]",
            "location": "northeurope",
            "properties": {
                "sku": "Standard",
                "containers": [
                    {
                        "name": "[parameters('containerGroups_selenium_search_app_name')]",
                        "properties": {
                            "image": "***/selenium-search:v1",
                            "ports": [
                                {
                                    "protocol": "TCP",
                                    "port": 4444
                                },
                                {
                                    "protocol": "TCP",
                                    "port": 7900
                                }
                            ],
                            "environmentVariables": [],
                            "resources": {
                                "requests": {
                                    "memoryInGB": 2,
                                    "cpu": 1
                                }
                            }
                        }
                    }
                ],
                "initContainers": [],
                "imageRegistryCredentials": [
                    {
                        "server": "***",
                        "username": "***"
                    }
                ],
                "restartPolicy": "Always",
                "ipAddress": {
                    "ports": [
                        {
                            "protocol": "TCP",
                            "port": 4444
                        },
                        {
                            "protocol": "TCP",
                            "port": 7900
                        }
                    ],
                    "ip": "*.***.**.**",
                    "type": "Public",
                    "dnsNameLabel": "selenium-search-dns",
                    "autoGeneratedDomainNameLabelScope": "Unsecure"
                },
                "osType": "Linux"
            }
        }
    ]
}
Relevant log output
No output
Operating System

Linux

Docker Selenium version (image tag)

4.22.0

Selenium Grid chart version (chart version)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the Azure Container Instance deployment template and the selenium/chrome_standalone image configuration, focusing on the declared ports 4444 and 7900. Reproduce the deployment and verify whether the VNC endpoint is reachable; done means identifying and documenting or correcting the configuration needed for the reported VNC connection.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, docker
Domain
cloud, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.