How to execute Playwright memory leak workaround script ?

[jpbaril]

If I understand correctly the workaround script shown on linked page below has a command that should be executed locally in the container itself.

https://github.com/dgtlmoon/changedetection.io/wiki/Playwright-content-fetcher#playwright-memory-leak

How can it be executed in a scripted manner?
Thank you

[ammgws]

I wonder if this would also work as an alternative to the workaround script?

https://docs.browserless.io/docs/docker.html#exit-on-health-failure

[me1299]

If I understand correctly the workaround script shown on linked page below has a command that should be executed locally in the container itself.

https://github.com/dgtlmoon/changedetection.io/wiki/Playwright-content-fetcher#playwright-memory-leak

How can it be executed in a scripted manner? Thank you

No it's not to be executed on the container itself. You execute it on the host of the container. It kills the process that is within the container.

[mmotti]

I'm a little confused by this one too. Am I correct in assuming that by running the command exactly as it is, it will somehow run within the correct docker container and not on the host system? I'm not sure exactly how it works but I certainly don't have the ./changedetection.py on my host.

[me1299]

I'm a little confused by this one too. Am I correct in assuming that by running the command exactly as it is, it will somehow run within the correct docker container and not on the host system? I'm not sure exactly how it works but I certainly don't have the ./changedetection.py on my host.

All processes running in docker containers are effectively running on your host system. You should have a changedection.py executing on your host when you have a docker container running exactly that.

By killing the changedetection.py process on your host you are actually killing the process within the docker container.