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

Cannot read properties of undefined when following the docker example #11

Open
strogonoff opened this issue Nov 18, 2022 · 2 comments
Open

Comments

@strogonoff
Copy link

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Cannot read properties of undefined (reading 'close') URL: https://www.wikipedia.org
Stack: TypeError: Cannot read properties of undefined (reading 'close')
    at Object.exports.getPageData (/usr/src/app/node_modules/single-file-cli/back-ends/puppeteer.js:54:15)
    at async capturePage (/usr/src/app/node_modules/single-file-cli/single-file-cli-api.js:254:20)
    at async runNextTask (/usr/src/app/node_modules/single-file-cli/single-file-cli-api.js:175:20)
    at async Promise.all (index 0)
    at async capture (/usr/src/app/node_modules/single-file-cli/single-file-cli-api.js:126:2)
    at async run (/usr/src/app/node_modules/single-file-cli/single-file:54:2)

Docker version 20.10.20, build 9fdeb9, macOS

@strogonoff strogonoff changed the title Cannot read properties of undefined when following the docker example Cannot read properties of undefined when following the docker example Nov 18, 2022
@gildas-lormeau
Copy link
Owner

I'm not sure the image works on ARM. You're a bit lucky because I own a Mac for about 1 week. I did not install Docker yet though. I'll do some tests.

@strogonoff
Copy link
Author

strogonoff commented Nov 20, 2022

To be honest I am not sure ARM is of consequence, since the image was built using amd64 platform (and it showed up as such in Docker Desktop GUI). Docker Desktop for Mac handles non-ARM architecture transparently using Apple’s compatibility layer. Judging by the error, it could be more likely some dependency became incompatible? That said, I did not dig in yet, will try when I have the time.

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

2 participants