Open inkwell84 opened 8 months ago
Unfortunately, that error message is to vague to lead to a solution. Perhaps you can make Portainer give you more detailed error messages, console logs, etc.
As a last resort, you can always use docker
to run docker containers, instead of Portainer or other tools that add complexity (and room for error) on top:
docker run --rm -it -v "$PWD:/volume1" -v data:/data -p 5452:5452 rednoah/filebot:node
Any idea where I’d find logs etc in Portainer?
On Fri, Dec 29, 2023 at 07:52 Reinhard Pointner @.***> wrote:
Unfortunately, that error message is to vague to lead to a solution. Perhaps you can make Portainer give you more detailed error messages, console logs, etc.
As a last resort, you can always use docker to run docker containers, instead of Portainer or other tools that add complexity (and room for error) on top:
docker run --rm -it -v "$PWD:/volume1" -v data:/data -p 5452:5452 rednoah/filebot:node
— Reply to this email directly, view it on GitHub https://github.com/filebot/filebot-docker/issues/19#issuecomment-1872060290, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMZ5V7MLLCXJBPCIZ4GJI2TYL24KFAVCNFSM6AAAAABBGJ7LVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGA3DAMRZGA . You are receiving this because you authored the thread.Message ID: @.***>
Unfortunately, I don't use Portainer.
Getting the above error from Portainer when trying to deploy filebot node via the stack editor.