[FEAT] Allow user to enable remote debugging port

[CliffHan]

Is this a new feature request?

• I have searched the existing issues

Wanted change

User may want to control chrome in container, to do some automatic staff.

I've tried to use CHROME_CLI, but it's not working.

Reason for change

I want to enable remote debugging for chrome in container. Here's my docker-compose.yml, with CHROME_CLI set:

---
services:
  chrome:
    image: linuxserver/chrome:latest
    container_name: chrome
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Shanghai
      - SELKIES_MANUAL_WIDTH=1280
      - SELKIES_MANUAL_HEIGHT=720
      - CHROME_CLI="--remote-debugging-address=0.0.0.0 --remote-debugging-port=9222"
    volumes:
      - ./config:/config
    ports:
      - 4000:3000
      - 4001:3001
      - 9222:9222
    shm_size: "1gb"
    restart: unless-stopped

But it's not working. When I use exec bash to check ports in container, I found port 9222 was not listening, while 3000/3001/8082 works as expected.

Not sure if this is a bug.

Proposed code change

No response

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Roxedus]

The quotes are working against you, quote the whole line.

https://docs.linuxserver.io/general/docker-compose/#quoting-variables

[CliffHan]

The quotes are working against you, quote the whole line.引号正在对你产生反效果，引用整行。

https://docs.linuxserver.io/general/docker-compose/#quoting-variables

I tried to quote whole line like this:
- "CHROME_CLI=--remote-debugging-address=0.0.0.0 --remote-debugging-port=9222"

rebuild the docker-compose, but still no luck

root@a9c260678224:/# ss -tunlp
Netid  State   Recv-Q  Send-Q    Local Address:Port      Peer Address:Port  Process
udp    UNCONN  0       0            127.0.0.11:54147          0.0.0.0:*
tcp    LISTEN  0       511             0.0.0.0:3000           0.0.0.0:*      users:(("nginx",pid=264,fd=5))
tcp    LISTEN  0       511             0.0.0.0:3001           0.0.0.0:*      users:(("nginx",pid=264,fd=7))
tcp    LISTEN  0       4096         127.0.0.11:33967          0.0.0.0:*
tcp    LISTEN  0       100             0.0.0.0:8082           0.0.0.0:*
tcp    LISTEN  0       511                [::]:3000              [::]:*      users:(("nginx",pid=264,fd=6))
tcp    LISTEN  0       511                [::]:3001              [::]:*      users:(("nginx",pid=264,fd=8))

[CliffHan]

my bad, missing a mandatory parameter "--user-data-dir"

closed

[arunpt]

@CliffHan Hey, did you find a solution for this? I'm also trying to expose the debug port but it doesn't seems to be working.

[ja14000]

@CliffHan Hey, did you find a solution for this? I'm also trying to expose the debug port but it doesn't seems to be working.

Same here, I've added:
CHROME_CLI=--remote-debugging-address=0.0.0.0 --remote-debugging-port=9222

but it doesn't work

$ ss -tulnp

Netid             State              Recv-Q              Send-Q                           Local Address:Port                           Peer Address:Port             Process
tcp               LISTEN             0                   100                                    0.0.0.0:8082                                0.0.0.0:*                 users:(("selkies",pid=352,fd=12))
tcp               LISTEN             0                   511                                    0.0.0.0:3000                                0.0.0.0:*                 users:(("nginx",pid=386,fd=5),("nginx",pid=385,fd=5),("nginx",pid=384,fd=5),("nginx",pid=383,fd=5),("nginx",pid=382,fd=5),("nginx",pid=381,fd=5),("nginx",pid=380,fd=5),("nginx",pid=379,fd=5),("nginx",pid=308,fd=5))
tcp               LISTEN             0                   511                                    0.0.0.0:3001                                0.0.0.0:*                 users:(("nginx",pid=386,fd=7),("nginx",pid=385,fd=7),("nginx",pid=384,fd=7),("nginx",pid=383,fd=7),("nginx",pid=382,fd=7),("nginx",pid=381,fd=7),("nginx",pid=380,fd=7),("nginx",pid=379,fd=7),("nginx",pid=308,fd=7))
tcp               LISTEN             0                   511                                       [::]:3000                                   [::]:*                 users:(("nginx",pid=386,fd=6),("nginx",pid=385,fd=6),("nginx",pid=384,fd=6),("nginx",pid=383,fd=6),("nginx",pid=382,fd=6),("nginx",pid=381,fd=6),("nginx",pid=380,fd=6),("nginx",pid=379,fd=6),("nginx",pid=308,fd=6))
tcp               LISTEN             0                   511                                       [::]:3001                                   [::]:*                 users:(("nginx",pid=386,fd=8),("nginx",pid=385,fd=8),("nginx",pid=384,fd=8),("nginx",pid=383,fd=8),("nginx",pid=382,fd=8),("nginx",pid=381,fd=8),("nginx",pid=380,fd=8),("nginx",pid=379,fd=8),("nginx",pid=308,fd=8))

[Kenxu2022]

@arunpt @ja14000 I’ve encountered the same issue and found that it is caused by a change on the Chrome side. Starting from Chrome 136, the behavior of the --remote-debugging-port switch has changed due to security concerns. You must explicitly specify --user-data-dir to enable remote debugging.

Based on my research, Chrome has not respected the --remote-debugging-address flag for a long time, meaning the remote debugging service is effectively forced to bind to localhost. As a result, consider using port forwarding instead if remote access is needed.

related:
https://developer.chrome.com/blog/remote-debugging-port
https://issues.chromium.org/issues/40242234

[jesset]

- "CHROME_CLI=--user-data-dir=/config/path/to/non-default-dir --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0"

I've got this working, the most important is set --user-data-dir= to a non-default data directory.

Cause chrome startup log says this:

DevTools remote debugging requires a non-default data directory. Specify this using --user-data-dir.