Can you update your Dockerfile to match the structure in the repo? It’s now copying the docker-entrypoint file into the working directory rather than the root one:
N8N image is working fine with https and our ssl certificate.
But we are getting error while running the n8n custom image.
I am attaching the screenshot for reference.
Can you help us in this.
Hey @abhilash,
can you also make sure to build a new image using docker build --no-cache. I remember this happened to me once and I could fix it buy making sure I run a new build. Don’t know why it happened though.
@marcus@MutedJam can you please help us in the docker file. We are trying to build custom image. But we are getting this deprecated some packages error. It was working fine like we were able to build the image and not to run the docker-compose but now we are not able build the custom docker image with same code.
Hi @abhilash, so you’re seeing the exact same error message as @AnjanaSAcroUser? ERR_SOCKET_TIMEOUT suggests a network problem, so you might need to look into this from your end.
Also, are you using the current master branch of the n8n repository? The Dockerfile has been updated very recently: n8n/docker/images/n8n-custom at master · n8n-io/n8n · GitHub. I’ve just tested this and after running npm install, the docker build command finished as expected:
Hi @MutedJam
Anjana and I are working together on this issue.
Yes we are using latest n8n dockerfile. 2-3 days back only we have take the recent code from n8n. Can you pls elaborate on network problem.
Hi @abhilash, as per your screenshot, this error suggests a problem related to network connectivity, perhaps because of a very restrictive firewall or proxy configuration. Are you also facing trouble building the image on a different network?
Hi @MutedJam
The machine I am working on don’t have any firewall restrictions. On same machine I was able to build the docker image few days back with the same code and let me verify for other environments.
Hm, I am afraid I don’t know what could cause the problem then. Perhaps you can share your current dockerfile and docker entrypoint so I can give this a go on my end?
Hi @abhilash, the Dockerfile provided by n8n has changed quite a bit. For example, it no longer uses the root user but the node user. The entrypoint file is executed from the working dir, not the root directory.
Could you update your own files using the files provided by n8n and give this another go?
Hi @MutedJam
I have taken the recent code from n8n repo.
Still while building custom docker image I am getting error.
Attaching the screenshot of error.