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

ERR_NAME_NOT_RESOLVED #15

Open
thyeestes opened this issue Jul 30, 2024 · 4 comments
Open

ERR_NAME_NOT_RESOLVED #15

thyeestes opened this issue Jul 30, 2024 · 4 comments

Comments

@thyeestes
Copy link

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
Copy link
Owner

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

@thyeestes
Copy link
Author

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
Copy link

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 : coreos/fedora-coreos-tracker#1790

@thyeestes
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants