-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
Has anyone tested this on 4.0.X? #618
Comments
Still works for me. I just had to:
|
Hi, I believe these questions should go in discussions and it had already been answered |
This seems to have got me back up and running as well. |
I just have this script run at boot-up, so it ran without a hick-up after the upgrade. |
Did you also do an "apt upgrade"? On my brand new Cloud Gateway Max with Unifi OS 4.0.6 I am not able to start the container..... |
An "update" retrieves the current status of the package lists from the repo. An "upgrade" only updates packages that have already been installed. If a new firmware version is installed, the additionally installed packages are removed. So you only need the current package list and can install the required packages again. An "update" is therefore exactly the right thing to do. |
Can someone please enlighten me about this script? I have now 4.0.6 on my UDM Pro SE and I can't install podman, so I don't know what I'm doing wrong but if I am understanding correctly you all have the version 4.x.x and after this script you can all run podman containers normally?
|
@yetisbey No, podman hasn't been a thing since 2.x. The script you mentioned allows for an alternative way of running your apps inside a light-weight namespace container. |
I'm curious, I try to setup tailsacle on my udmse on 4.0.6. So I need container-common, the instructions do not work for 4.0.6, so it seems some missing parts are here.
I'm lost... If anyone know how to get this working so I can install tailscale I would appreciate |
|
Hi,
Has anyone have possibility to try this on 4.0.x releases?
Thanks in advance!
The text was updated successfully, but these errors were encountered: