search

dgtlmoon / sockpuppetbrowser

A scalable server for providing Chrome interfaces where needed
Apache License 2.0
32 stars 8 forks source link

ERR_NAME_NOT_RESOLVED #15

Open thyeestes opened 3 months ago

thyeestes commented 3 months ago

I am experiencing a strange issue with running this in a Podman container. When I use this image then I get ERR_NAME_NOT_RESOLVED error, e.g. with this site https://www.asuswrt-merlin.net/.

When I use a browserless image like ghcr.io/browserless/chrome:latest it renders just fine.

Any ideas how to solve?

Thanks

dgtlmoon commented 3 months ago

Hmm not enough information, can you show the whole docker-compose.yml ?

thyeestes commented 3 months ago

Sure. However I am using Podman quadlets: `[Container]

Image=ghcr.io/browserless/chrome:latest

Image=docker.io/dgtlmoon/sockpuppetbrowser:latest AddCapability=SYS_ADMIN AutoUpdate=registry ContainerName=cd-browserless Network=proxy.network Environment=TZ=Europe/Amsterdam Environment=SCREEN_WIDTH=1920 Environment=SCREEN_HEIGHT=1080 Environment=SCREEN_DEPTH=24 Environment=MAX_CONCURRENT_CHROME_PROCESSES=10 Environment=ENABLE_DEBUGGER=false Environment=PREBOOT_CHROME=true Environment=CONNECTION_TIMEOUT=300000 Environment=MAX_CONCURRENT_SESSIONS=10 Pod=changedetection.pod

[Container] Image=docker.io/dgtlmoon/changedetection.io:latest AutoUpdate=registry ContainerName=cd-changedetection Network=proxy.network Volume=$PWD/changedetection:/datastore Environment=TZ=Europe/Amsterdam Environment=LOGGER_LEVEL=DEBUG Environment=PLAYWRIGHT_DRIVER_URL=ws://cd-browserless:3000

Environment=PLAYWRIGHT_DRIVER_URL=ws://cd-browserless:3000/chrome?launch={"headless":false}

Pod=changedetection.pod`

skyblaster commented 2 months ago

I'm also using a Podman quadlet with Environment=PLAYWRIGHT_DRIVER_URL=ws://sockpuppetbrowser:3000 and seeing the same Exception: net::ERR_NAME_NOT_RESOLVED

My host is Fedora CoreOS and I see the last email received from changedetection.io was August 16th, with a host reboot on the 17th.

This appears to be a Podman, netavark, and/or passt issue. I just opened the following hoping the FCOS team can reproduce the issue and possibly expedite the promotion of testing to stable : https://github.com/coreos/fedora-coreos-tracker/issues/1790

thyeestes commented 2 months ago

I switched to slirp4netns, because of an issue with socket activation and Traefik, so I think you can take passt out of equation.