🐛 BUG: Wrangler doesn't work on my system/OS (provide a static build of workerd)
#3457
Comments
|
Also related to the discussion in cloudflare/workerd#46 |
|
FYI, it's also not works under Codespaces of Github, and could be really appreciate to make it works out-of-box as before with the wrangler v2.20. |
|
@lakano As of this morning, this is no longer true. The default Codespaces image has been upgraded to Debian 12 Bookworm. If you haven’t changed your configuration, you should just be able to run ‘Codespaces: Rebuild Container’, otherwise you can upgrade the base image (usually either For example, a minimum Codespaces setup is as follows:
|
|
Wrangler does not work on Debian 11 , I installed clang libc++-dev libc++abi-dev by apt install command , however, does not work correctly. Please let me know, I think Debian and Ubuntu are most popular Linux OS on Interent server. Thanks. -- log ? Compiled Worker successfully KV Namespaces: |
|
@gennai3 Hello! I noticed you’ve sent the same message to a few threads, so hopefully I can help you here. As explained above and on other threads you’ve posted to (in great detail), |
|
Thank you @huw for your support. I will try upgrde from Deabin 11 to Debian 12 soon. I hope Debian/Ubuntu will be work wrangler and Cloudfare product. Sorry that my multi post, thank you again. |
|
Hi |
|
Fedora users can install |
|
|
|
Hey everyone! 👋 We've just released a new On Linux,
Ubuntu 18.04 (which is now end-of-life) and Debian 10 will not be supported. On macOS, we now target macOS 11 "Big Sur" when building. This means any version of macOS 11 or higher (Big Sur, Monterey, Ventura, Sonoma) should be supported. I'm going to close this issue now, but please let us know if you encounter any issues. 🙂 |
|
Can't seem to install the latest beta
$ npm uninstall -g wrangler
removed 101 packages in 197ms$ npx wrangler@beta dev
Need to install the following packages:
wrangler@0.0.0-bcdc1fe5
Ok to proceed? (y) y
⛅️ wrangler 0.0.0-bcdc1fe5
---------------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler dev path/to/script`) or the `main` config field.
If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/chooseEnv:
|
It does work when installed directly into a project directory, though. 👍 |
Does this version contain the new I'd like to use the new TCP Socket API but it doesn't seem available: |
Testing with Remix (with Cloudflare Pages)
$ grep "cloudflare:sockets" -R node_modules/*
Binary file node_modules/@cloudflare/workerd-linux-64/bin/workerd matches
Binary file node_modules/workerd/bin/workerd matchespackage.json {
"private": true,
"sideEffects": false,
"type": "module",
"scripts": {
"build": "remix build",
"dev": "remix dev --no-restart -c \"npm run start\"",
"start": "wrangler pages dev --compatibility-date=2023-06-21 ./public",
"typecheck": "tsc"
},
"dependencies": {
"@remix-run/cloudflare": "^1.18.1",
"@remix-run/cloudflare-pages": "^1.18.1",
"@remix-run/css-bundle": "^1.18.1",
"@remix-run/react": "^1.18.1",
"isbot": "^3.6.8",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"remix-utils": "^6.5.0"
},
"devDependencies": {
"@cloudflare/workers-types": "^3.19.0",
"@remix-run/dev": "^1.18.1",
"@remix-run/eslint-config": "^1.18.1",
"@types/react": "^18.0.35",
"@types/react-dom": "^18.0.11",
"eslint": "^8.38.0",
"typescript": "^5.0.4",
"wrangler": "^0.0.0-3f61892d"
},
"engines": {
"node": ">=16.13.0"
}
} |
Testing with Cloudflare Workers
$ npm install -g wrangler@beta
$ wrangler generate worker-test-wrangler-beta$ wrangler dev
⛅️ wrangler 0.0.0-3f61892d
---------------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
⎔ Starting local server...
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-06-28",
but you've requested "2023-07-03". Falling back to "2023-06-28"...
[mf:inf] Ready on http://127.0.0.1:8787/
[mf:inf] GET / 200 OK (426ms)
[mf:inf] GET /favicon.ico 200 OK (494ms)Gopher over HTTP pageSo TCP socket does work with Workers. 👍 NB: Not sure why there are 2 versions of wrangler installed globally: $ wrangler -v
⛅️ wrangler 0.0.0-3f61892d$ wrangler2 -v
⛅️ wrangler 0.0.0-3f61892d |
wrangler and wrangler2 should both point to the same underlying script, so there's just two links to the same wrangler installation. For example, both of them point to Also wanted to note that with the new version 3.1.2 the extended OS support is now available in the stable release. As Brendan said above, please let us know if you encounter any more issues. |
I've started a basic React app with Pages and the general solution that seems to solve compatibility issues is to install Wrangler in the global scope and remove the reference of Wrangler in the It does work - locally - so far, although I have yet to deploy it. I'll give a try and test with the Wrangler 3.1.2 and let you know - I'm currently busy having fun with the new TCP socket Cheers. |
|
I was getting the "Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set" error on Mac OSX 13.4.1 (22F82) even with wrangler 3.1.2 installed. I had to remove wrangler from my package.json and then install it globally for everything to work. Is this the recommended setup going forward? |
@fhanau I've tested installation of a Remix project with Wrangler 3.1.2 and I'm getting the same error than above when importing the It looks like a Remix bug though, doesn't it ? Not sure why package.json{
"private": true,
"sideEffects": false,
"type": "module",
"scripts": {
"build": "remix build",
"dev": "remix dev --no-restart -c \"npm run start\"",
"start": "wrangler pages dev --compatibility-date=2023-06-21 ./public",
"typecheck": "tsc",
"pages:deploy": "npm run build && wrangler pages publish ./public"
},
"dependencies": {
"@remix-run/cloudflare": "^1.16.0",
"@remix-run/cloudflare-pages": "^1.16.0",
"@remix-run/css-bundle": "^1.16.0",
"@remix-run/react": "^1.16.0",
"isbot": "^3.6.8",
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@cloudflare/workers-types": "^3.19.0",
"@remix-run/dev": "^1.16.0",
"@remix-run/eslint-config": "^1.16.0",
"@types/react": "^18.0.35",
"@types/react-dom": "^18.0.11",
"eslint": "^8.38.0",
"typescript": "^5.0.4",
"wrangler": "^3.1.2"
},
"engines": {
"node": ">=16.13.0"
}
} |
@mrbbot Sounds like a problem more on the JS level right? |
|
@fhanau I suspect so, will try take a look at this soon 👍 |
@jbasdf I'm getting the same error (wrangler 3.2) and I cannot get rid of it (I've also tried out |
|
This is the full error I get with wrangler 3.2 (and also with beta) in macOS 13.14 |
I get a similar message after I edit the code with wrong syntax, the shell crashes but the process is still alive, then I can't restart the app because the address is already in use. I'm using |
|
This module still won't work. OS:Raspberry pi OS npm: |
npx wrangler@2.20.0 pages dev ./public ---persist-to ./pages --ip 127.0.0.1 --port 8111 |
I saw this comment #3432 (comment) about Big Sur being supported. I was on 11.1 and that didn't work for me, upgraded to macOS 14 and now it works. |
|
Not working in BunsenLabs GNU/Linux 10.5 (Lithium) |
Hi, as far as I can see BunsenLabs Lithium is based on Debian Buster and uses glibc 2.28, whereas workerd (and by extension wrangler) requires glibc 2.31 or higher. Please consider upgrading to Beryllium or higher. |
|
This is happening for me on wrangler@3.57.2 and Ubuntu 22.04. Using wrangler@2.20.0 works fine. |
Can you share the specific error message you see? Ubuntu 20.04 and 22.04 should be fully supported. |
A similar error happened with |
|
I got these commands working with wrangler@3.36.0 but not working with wrangler@3.37.0 and onwards. |
|
@pointatnick what's your platform? Is it Ubuntu on WSL1 by any chance? |
|
@dom96 Yes, Ubuntu on WSL1 |
|
@pointatnick I ran into a similar issue and recently switched to WSL2 which seems to have solved the problem. Can you give that a try as well? |
|
@dom96 I've tried before to upgrade to WSL2 but I am limited by my hardware. I trust upgrading would fix the issue, since it was hard finding WSL1 as an explanation for the bug. I'm good with using a slightly older version of wrangler for now. Thanks for the responses! |
Glad to hear that this works with WSL2. I tried to see what might cause the breakage with WSL1 – From prior discussion it sounds like the tcmalloc issue starts with wrangler@3.36.0...wrangler@3.37.0. |
Which Cloudflare product(s) does this pertain to?
Wrangler
What version of
Wranglerare you using?3
What operating system are you using?
N/A
Describe the Bug
Collection of issues related to Wrangler not working on specific systems/OSs which will be fixed by providing a static build of
workerd.wrangler devlocal development not working #3301Error: write EPIPEin WSL2 (Ubuntu 20.04.6 LTS) #3262The text was updated successfully, but these errors were encountered: