I have a problem with running a docker container.
First I ran the docker build command from my local Dockerfile:
docker build --build-arg N8N_VERSION=0.18.1 -t n8nio/n8n:0.18.1 .
Then I ran the docker run command:
docker run -it --rm --name n8n -p 5678:5678 n8nio/n8n:0.18.1
But I faced this error:
[FATAL tini (7)] exec /docker-entrypoint.sh failed: No such file or directory
But there is a docker-entrypoint.sh file in /docker/images/n8n directory!
Any idea what’s wrong with this?
Not sure I understand. Why do you build the image yourself and do not use the published version? And why do you then build a version with the code from probably over a year ago?
The number is literally the only thing that matters. It does not use any of the code in the project at all. All it does is to npm install the n8n version with that number you provide there.
If you want to do a real custom build with your local code, you have to use the n8n-custom docker file here:
Hi again.
My project had some ts errors, i fixed all via tslintfix command, also I checked for the errors by tslint command and it seems there isn’t any.
But when it comes to “npm run build” it raises some errors. The errors mostly relate to missing comma and indentation and it also ignores tslint disable lines! What are these? And is there any automatic command like tslintfix to fix them all? I can manually fix them except the tslint disable ones! It’s very weird!
Honestly no idea what is going wrong. But sounds like something got messed up. There are currently no issues on the master. You can see that here:
All the latest commits have a green checkmark and not a red cross.
Also should npm run tslintfix fix all the tslint issues that can be fixed (not the case for all but missing commas are one of the ones that can be fixed automatically).
I advice to check out again from master and build from there and see if it works. Then apply your changes again and see when and what breaks it.
Thank you very much @jan for the answer. I did exactly what you said and all error are fixed now and all codes are up to date. So I ran docker build on /n8n-custom directory and docker built an image successfully.
But the problem is: when I run it by the docker run command it throws this error:
[FATAL tini (7)] exec /docker-entrypoint.sh failed: No such file or directory
This file does exist in n8n-custom directory, not sure why this happens! Do you have any idea?
@jellybean Sorry totally overlooked your answer. Not sure if it still matters but have honestly no idea why that would happen. After all, is the second last command in the docker-file to copy that file into the image. If it is not working the build should fail.
@Joshua_Riley I did just rebuild n8n and all is working fine. Anyway saw that winston is not set as a dependency. Guess it worked always anyway as a dependency probably had it as an own dependency. Added it now directly. Maybe that fixes the problem for you. Make sure to pull first.
This looks like you’re having permission issues. Does the user who is executing the command (if not the root user) have the permission to run it? Also, are you running it as sudo?
So I’m not sure exactly how to make sure the user has permission, I’ve tried adding sudo to the start of them su-exec commands in the docker-endpoint.sh file but that didn’t work, I also tried adding sudo to the start of the entrypoint in the dockerfile and that didn’t work either,
