Hi @abhilash, this looks like one of the network requests is still failing for you as indicated by the ERR_SOCKET_TIMEOUT error. Can you try building the image from the current n8n repository without any changes, just to make sure none of your modifications is causing the problem?
Hi @MutedJam,
I tried to build the image without making any change to code.
Still its not working.
Please suggest how I can deal with ERR_SOCKET_TIMEOUT error.
Thanks & Regards,
Abhilash
I am afraid I don’t quite know what might be causing this on your side. As suggested, my first try would be using a different network (outside your company firewalls/proxy).
Hi @MutedJam,
I have tired over my own network still it giving me same error.
Hm, I am afraid I don’t have any other ideas here, but I am not exactly an expert when it comes to building docker images. Perhaps @netroy has any idea what else to check?
Hey @abhilash,
Can you send a screenshot of the error you get when running on your own network?
Hi @netroy,
can you pls help us in resolving the docker image issue.
Thanks
Hi @Jon,
I am getting the same error as I am getting on office network.
Hey @abhilash,
That looks like the same image, When we mentioned the network we don’t mean the local network of your machine we mean the network where the server is which I assume is in Azure looking at that username although I could be wrong.
ECONNRESET is not an error being thrown by n8n it is coming back when trying to get the packages, The first thing I would do is check the network where the server is to see if there are any issues there.
You could as a test run the docker build command on your desktop and see if it works there as well.
1 Like
Thanks @Jon.
I will check on local as well on different azure machine.
Hey @abhilash
Can you please make sure that you are on the latest master branch on the n8n repo, and if you are using a fork, can you please make sure that your fork is up-to-date?
The connection related errors mean that either there is some issue at the firewall, or your ISP is blocking these requests.
You can try to switch to an alternate registry by changing npm ci to npm --registry http://registry.yarnpkg.com install in the Dockerfile.
If that fails, please try changing the https in the registry url to http.
If either of these works, it’s possible that either your ISP, or a firewall is blocking requests to the NPM registry.
3 Likes
Thanks @netroy.
I will check this. I am using latest the code. I take the pull in morning only.
Thanks @MutedJam @Jon @netroy for all your valuable suggestions, I am able to create custom n8n image.
But after creating the custom docker image. I tried to run the docker-compose command to run the docker. There I am getting the errors. I am attaching the screenshot for error details. I have keep docker-compose.yml in n8n root folder along with .env file.
Please guide me as well where I can keep docker-compose.yml file.
Thanks & Regards,
Abhilash
@MutedJam
Can you please suggest any solution for above issue
Hi @abhilash, this sounds like a permission problem. Are you also facing this issue when using a new docker volume rather than an existing one?
Hi @MutedJam,
Yes I am still facing the same issue even with the new docker volume.
can you please tell which kind of permission and where I need to give the permission.
I am afraid I am not sure what might cause the behaviour here. Let me try building the image once again using the current codebase and see if I can reproduce the problem.
sure, Thanks a lot.
Hm, both build and run are working as expecting for me:
So I am afraid based on the information you have provided I am not able to reproduce the problem 
Perhaps @netroy has any other idea here?
Hi @MutedJam,
I am trying to run this command to run the docker
docker run -it --rm -p 5678:5678 -v ~/.n8n:/home/node/.n8n n8n-custom:latest
we are using postgres as our database. I have made the changes in schema.ts and make postgres as default database but while running the command. I am getting error as "There was an error initializing DB: “SQLITE_CANTOPEN: unable to open database file”
Can you please help us why we are getting this error. anywhere do we need to change the parameter like in we have did in schema.ts file.
Attaching the screenshot for detail error.
Thanks & Regards,
Abhilash