Did you get it working?

G

My container is being killed randomly... @Mike Nomitch how can I see the reason?

R

rufi•7/5/25, 1:05 AM

I can deploy my containers and it works remotely, but I cannot run them locally in dev mode, I get: "A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset." (...) "container error: Failed to verify port 8000 is available after 27 attempts, last error: internal error; reference = vs98k.."

Rrufi I can deploy my containers and it works remotely, but I cannot run them locally ...

L

lupin•7/5/25, 12:46 PM

Same here :NotLikeThis:

R

Radu•7/5/25, 6:06 PM

  const response = await container.containerFetch("http://container/to-markdown", {
    method: "POST",
    headers: {
      "Content-Type": "multipart/form-data",
      "Content-Disposition": `form-data; name="file"; filename="${file.name}"`,
    },
    body: formData,
  });

  const response = await container.containerFetch("http://container/to-markdown", {
    method: "POST",
    headers: {
      "Content-Type": "multipart/form-data",
      "Content-Disposition": `form-data; name="file"; filename="${file.name}"`,
    },
    body: formData,
  });

  const response = await container.containerFetch("http://container/to-markdown", {
    method: "POST",
    headers: {
      "Content-Type": "multipart/form-data",
      "Content-Disposition": `form-data; name="file"; filename="${file.name}"`,
    },
    body: formData,
  });

  const response = await container.containerFetch("http://container/to-markdown", {
    method: "POST",
    headers: {
      "Content-Type": "multipart/form-data",
      "Content-Disposition": `form-data; name="file"; filename="${file.name}"`,
    },
    body: formData,
  });

✘ [ERROR] DOMException {

code: 25,
name: 'DataCloneError',
message: 'Could not serialize object of type "FormData". This type does not support
serialization.',
stack: 'DataCloneError: Could not serialize object of type "FormData". This type does not
support serialization.\n' +

is this not implemented?

M

Mr. Technician•7/5/25, 6:13 PM

12:55:42.975    #4 ERROR: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.846    ------
12:55:53.851     > [1/1] FROM ghcr.io/browserless/chromium:latest@sha256:ca1cb28a74a7658175057711ca2b2f68b4eb72a2897b2515d2dac124a4a5d70b:
12:55:53.852    ------
12:55:53.853    Dockerfile:1
12:55:53.853    --------------------
12:55:53.853       1 | >>> FROM ghcr.io/browserless/chromium:latest
12:55:53.853       2 |     
12:55:53.853       3 |     ENV \
12:55:53.853    --------------------
12:55:53.853    ERROR: failed to build: failed to solve: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.869    
12:55:53.983    ✘ [ERROR] Build exited with code: 1

12:55:42.975    #4 ERROR: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.846    ------
12:55:53.851     > [1/1] FROM ghcr.io/browserless/chromium:latest@sha256:ca1cb28a74a7658175057711ca2b2f68b4eb72a2897b2515d2dac124a4a5d70b:
12:55:53.852    ------
12:55:53.853    Dockerfile:1
12:55:53.853    --------------------
12:55:53.853       1 | >>> FROM ghcr.io/browserless/chromium:latest
12:55:53.853       2 |     
12:55:53.853       3 |     ENV \
12:55:53.853    --------------------
12:55:53.853    ERROR: failed to build: failed to solve: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.869    
12:55:53.983    ✘ [ERROR] Build exited with code: 1

12:55:42.975    #4 ERROR: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.846    ------
12:55:53.851     > [1/1] FROM ghcr.io/browserless/chromium:latest@sha256:ca1cb28a74a7658175057711ca2b2f68b4eb72a2897b2515d2dac124a4a5d70b:
12:55:53.852    ------
12:55:53.853    Dockerfile:1
12:55:53.853    --------------------
12:55:53.853       1 | >>> FROM ghcr.io/browserless/chromium:latest
12:55:53.853       2 |     
12:55:53.853       3 |     ENV \
12:55:53.853    --------------------
12:55:53.853    ERROR: failed to build: failed to solve: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.869    
12:55:53.983    ✘ [ERROR] Build exited with code: 1

12:55:42.975    #4 ERROR: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.846    ------
12:55:53.851     > [1/1] FROM ghcr.io/browserless/chromium:latest@sha256:ca1cb28a74a7658175057711ca2b2f68b4eb72a2897b2515d2dac124a4a5d70b:
12:55:53.852    ------
12:55:53.853    Dockerfile:1
12:55:53.853    --------------------
12:55:53.853       1 | >>> FROM ghcr.io/browserless/chromium:latest
12:55:53.853       2 |     
12:55:53.853       3 |     ENV \
12:55:53.853    --------------------
12:55:53.853    ERROR: failed to build: failed to solve: failed to register layer: write /usr/src/app/node_modules/playwright-1.51/lib/vite/recorder/assets/codeMirrorModule-B9YMkrwa.js: no space left on device
12:55:53.869    
12:55:53.983    ✘ [ERROR] Build exited with code: 1

M

Mr. Technician•7/5/25, 6:13 PM

can I get a file space increase pretty please?

M

Mr. Technician•7/5/25, 7:35 PM

    ✘ [ERROR] Image too large: needs 2467 MB, but your app is limited to images with size 2000 MB. Your account needs more disk size per instance to run this container. The default disk size is 2GB.

    ✘ [ERROR] Image too large: needs 2467 MB, but your app is limited to images with size 2000 MB. Your account needs more disk size per instance to run this container. The default disk size is 2GB.

    ✘ [ERROR] Image too large: needs 2467 MB, but your app is limited to images with size 2000 MB. Your account needs more disk size per instance to run this container. The default disk size is 2GB.

    ✘ [ERROR] Image too large: needs 2467 MB, but your app is limited to images with size 2000 MB. Your account needs more disk size per instance to run this container. The default disk size is 2GB.

M

Mr. Technician•7/5/25, 7:35 PM

MMr. Technician ``` ✘ [ERROR] Image too large: needs 2467 MB, but your app is limited to imag...

A

Alex•7/5/25, 8:23 PM

Update ur docker ignore file. 2GB mostly enough even for a large projects.

AAlex Update ur docker ignore file. 2GB mostly enough even for a large projects.

M

Mr. Technician•7/5/25, 8:24 PM

can i do this when all im doing is pulling an existing image?

M

Mr. Technician•7/5/25, 8:24 PM

i’m not surprised it’s big since both images i tested include Chromium

A

Alex•7/5/25, 8:26 PM

You can get original dockerfile and drop the stuff you don't need. I would start from that point

AAlex You can get original dockerfile and drop the stuff you don't need. I would start...

M

Mr. Technician•7/5/25, 10:39 PM

ah ok, i doubt there much i can drop unfortunately

6

619napster•7/5/25, 11:10 PM

The code below was working fine a day ago
but now I am getting this error
anything I have missed ?
I was not calling start before as well

6

619napster•7/5/25, 11:59 PM

Never mind i just missed a pacakge in requirements.txt

M

Muhammad•7/6/25, 6:37 AM

I'm getting: Container suddenly disconnected, try again

it's working perfectly on localhost but once I deploy I get the error

IIsaac McFadyen No, if you use one Worker and then add multiple `containers` (in your wrangler.j...

J

jaden•7/7/25, 2:06 AM

In our current architecture, I want it to be similar to "worker for platform." A worker can mount multiple containers (services) and use subdomains to distribute traffic to different containers. Currently, when I look at the deployment process, containers are represented as an array. In this case, it seems that deploying multiple containers simultaneously is not feasible, as this is a distributed scenario where several deployments may occur at the same time. How can this be handled?