I ruined my docker setup

Hi, I tried to update my N8N to the latest version. But since I’m a docker Noob, I ruined it. Can anybody tell me what commands I need to run to restore my n8n setup?

Please let me know if you need any other information.
I run Docker on a vps, so only have novnc commandline access.

Any advice on how to update without mistakes, is also welcome.


## Information on your n8n setup
- **n8n version:** (no working version now)
- **Database (default: SQLite):**
- **n8n EXECUTIONS_PROCESS setting (default: own, main):** ?
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** DOCKER
- **Operating system:**  UBUNTU
I just found out it seems my n8n wass installed using docker compose.

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

What is it that is ruined? When using Docker to update n8n, it is usually enough to change the image version number in your docker compose file and then restart. Doing that, n8n should be updated without affecting any other part of your system, including workflows, credentials, etc.

To restore your n8n with Docker, set the previous version number in your docker compose file and restart.
For example, if you want to updatde/revert to version 1.78.1, set your image like so in your docker compose file: image: n8nio/n8n:1.78.1

1 Like

Thanks for your suggestion. I guess I removed my image and now the port and enrtypoint settings are lost. But I will try to use compose.

It was my mistake I didn’t know compose was used. So I followed the regular instructions and removed the traefik image. There I guess it went wrong there.

I guess I will have to wait and monday ask the genius of my hosting company who installed it for me, to fix it. Docker in command line is not fool proof :wink:

1 Like

It seems like there are some conflicts in your n8n docker. I sugguest you implement restoration and update steps : 1. stop existing containers;2. backup critical data(important);3. clean up old containers;4. fresh Installation. You could input my answer as a prompt in LLM to get terninal code . good luck bro

1 Like

My hosting company restarted N8N using compose, and it works again…no data loss, and updated to latest version.

So it seems:
if you used compose, you should not try to update the ‘normal’ way. That was my mistake. Besides not knowing what I was doing. But I guess thats the way most developpers learned their job… :wink:

1 Like

I think you shuld do,

  1. check your container
  2. delete unsed container
  3. download latest n8n version
  4. again create n8n container
  5. verify n8n

Hope it work for you

Thanks for your instructions. I hired a professional. So it’s up and running again. :slight_smile:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.