Nicola
Nicola
You need to supply the `-it` parameter to docker, as per README: > docker run --rm -it browsh/browsh
It has been effective for me, but it may change with newer versions. To stay on the safe side, but still avoid failing, I see 2 options: * wrap the...
I progressed on the fork. I converted the code to use OOP (objects), since it looks more logical to me (we have 2 pieces of code, one for Emby, the...
According to [the cheatsheet](https://python-future.org/compatible_idioms.html#configparser) it does
What about instead enabling mypy type checking and avoid a series of checks used probably by a single caller? Nicola Canepa Il giorno 12 mag 2024, 14:41, alle ore 14:41,...
Hi, I was about to post the same. I did the workaround with `privileged: true`, but it seems the correct way would be to change the base image in `Dockerfile`...
How can this be closed without a fix?
Sorry: I saw the "mentioned" appear while writing... The problem is Docker compatibility with the base image (according to [this thread](https://stackoverflow.com/questions/76955036/build-started-failing-using-python3-8-docker-image-on-apt-get-update-and-instal)). Would it be possible to rebuild the image with...
> First of all its not closed. Second, it seems to be a problem with your system/os/docker version rather than this repository. If the bug is in another piece of...
One more note: after rebuilding the image on my raspberry, it now works perfectly (without `privileged: true`), since I have Docker 20.10.5 there. Do you think it would be possible...