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

Has anyone tested this on 4.0.X? #618

Open
yetisbey opened this issue Jul 1, 2024 · 10 comments
Open

Has anyone tested this on 4.0.X? #618

yetisbey opened this issue Jul 1, 2024 · 10 comments

Comments

@yetisbey
Copy link

yetisbey commented Jul 1, 2024

Hi,

Has anyone have possibility to try this on 4.0.x releases?

Thanks in advance!

@r3dshell
Copy link

r3dshell commented Jul 2, 2024

Still works for me. I just had to:

apt update
apt -y install systemd-container debootstrap
machinectl start debian-custom
machinectl enable debian-custom

@Dr-Shadow
Copy link

Hi,

I believe these questions should go in discussions and it had already been answered

https://github.com/orgs/unifi-utilities/discussions/604

@MRobi1
Copy link

MRobi1 commented Jul 6, 2024

Still works for me. I just had to:

apt update
apt -y install systemd-container debootstrap
machinectl start debian-custom
machinectl enable debian-custom

This seems to have got me back up and running as well.

@pedropombeiro
Copy link
Contributor

Still works for me. I just had to:

apt update
apt -y install systemd-container debootstrap
machinectl start debian-custom
machinectl enable debian-custom

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.

@massaquah
Copy link

Did you also do an "apt upgrade"?
An "update" alone shouldn't do anything on it's own...

On my brand new Cloud Gateway Max with Unifi OS 4.0.6 I am not able to start the container.....

@techsolo12
Copy link

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.

@yetisbey
Copy link
Author

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?

Still works for me. I just had to:

apt update
apt -y install systemd-container debootstrap
machinectl start debian-custom
machinectl enable debian-custom

@pedropombeiro
Copy link
Contributor

@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.

@llaforest
Copy link
Contributor

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 can install systemd-container deboostrap but there is no image in the machinectl, it needs to be imported somehow. I tried importing one with this but it seems the image is not in the good format

machinectl pull-tar --verify=no https://cloud.debian.org/images/cloud/bullseye/latest/debian-11-nocloud-arm64.tar.xz

machinectl start debian-11-nocloud-arm64Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xe" for detail

I'm lost... If anyone know how to get this working so I can install tailscale I would appreciate

@gatesry
Copy link
Contributor

gatesry commented Sep 16, 2024

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 can install systemd-container deboostrap but there is no image in the machinectl, it needs to be imported somehow. I tried importing one with this but it seems the image is not in the good format

machinectl pull-tar --verify=no https://cloud.debian.org/images/cloud/bullseye/latest/debian-11-nocloud-arm64.tar.xz

machinectl start debian-11-nocloud-arm64Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xe" for detail

I'm lost... If anyone know how to get this working so I can install tailscale I would appreciate

Check https://github.com/SierraSoftworks/tailscale-udm

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

9 participants