Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.2.2 to 1.3 update failed: Mender not installed #1955

Closed
bocekm opened this issue Dec 11, 2024 · 2 comments
Closed

1.2.2 to 1.3 update failed: Mender not installed #1955

bocekm opened this issue Dec 11, 2024 · 2 comments

Comments

@bocekm
Copy link

bocekm commented Dec 11, 2024

I'm running Umbrel 1.2.2 in a docker container on Synology NAS installed per https://mariushosting.com/how-to-install-umbrel-os-on-your-synology-nas/ (thanks, @mariushosting).

When I try to update to 1.3 through the web UI, I get Error: Mender not installed.
Screenshot from 2024-12-11 22-21-01

What's the best way to go about it?
Is there anything missing in the Docker compose file mentioned in the article?

services:
  umbrel:
    image: dockurr/umbrel
    container_name: Umbrel-OS
    healthcheck:
       test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/80' || exit 1
       interval: 10s
       timeout: 5s
       retries: 3
       start_period: 90s
    ports:
      - 3253:80
    volumes:
      - /volume1/docker/umbrel:/data:rw
      - /var/run/docker.sock:/var/run/docker.sock
    restart: on-failure:5
@mariushosting
Copy link

I'm running Umbrel 1.2.2 in a docker container on Synology NAS installed per https://mariushosting.com/how-to-install-umbrel-os-on-your-synology-nas/ (thanks, @mariushosting).

When I try to update to 1.3 through the web UI, I get Error: Mender not installed. Screenshot from 2024-12-11 22-21-01

What's the best way to go about it? Is there anything missing in the Docker compose file mentioned in the article?

services:
  umbrel:
    image: dockurr/umbrel
    container_name: Umbrel-OS
    healthcheck:
       test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/80' || exit 1
       interval: 10s
       timeout: 5s
       retries: 3
       start_period: 90s
    ports:
      - 3253:80
    volumes:
      - /volume1/docker/umbrel:/data:rw
      - /var/run/docker.sock:/var/run/docker.sock
    restart: on-failure:5

You should update it via Portainer Method 3 https://mariushosting.com/synology-how-to-update-docker-image/ not the web gui.

@bocekm
Copy link
Author

bocekm commented Dec 12, 2024

Ok, I had recreated+repulled the umbrel container in Portainer but the logs then showed:

❯ Starting umbrelOS for Docker v1.3.0...
❯ For support visit https://github.com/dockur/umbrel/issues
Error response from daemon: Container ee513a0ff0179206c96cf300b45b4ee5953fc879c33c01987a3a95f6a297587b is marked for removal and cannot be connected or disconnected to the network
❯ ERROR: Failed to connect container to network!
❯ Starting umbrelOS for Docker v1.3.0...
❯ For support visit https://github.com/dockur/umbrel/issues
❯ ERROR: Failed to find a container with name: 'ee513a0ff017'!

I found the ee513a0ff017 under the container network hostname.
Screenshot From 2024-12-12 15-54-41
So I stopped the container, edited it and removed the hostname, re-deployed, and now it runs fine. Thanks for the poiners.

@bocekm bocekm closed this as completed Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants