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

Successfull upgrade from Pimox6to7 #1

Closed
semool opened this issue Aug 18, 2021 · 3 comments
Closed

Successfull upgrade from Pimox6to7 #1

semool opened this issue Aug 18, 2021 · 3 comments

Comments

@semool
Copy link

semool commented Aug 18, 2021

I set it as issue :) but it is a success Message.
I have edit all source files to Bullseye and Pimox7 and made a dist-upgrade.
All went smooth and working fine now with v7.
Big Thanks for your great work to contribute this Packages to us.

@celangoni
Copy link

I can confirm!
I need to reinstall pve-manager, but all configuration are kept.
Thanks for an amazing job!

@Glutamat42
Copy link

can confirm it too. I didn't had to reinstall pve-manager. After update i had to do a force refresh in the web interface (strg shift r) to make the statistics working. Sadly i cant start one of my containers, but everything else looks fine (just had a quick look on it, also didn't look into why the container isn't starting anymore after the update)

Interestingly i failed installing pimox7 when i first updated to bullseye (raspbian) and then tried to install pimox7. apt failed with a dependency error (dont remember the exact error message). Now i first installed pimox6 und then updated to bullseye + pimox7 in one step and it worked.

@Glutamat42
Copy link

The problem i have with this one container seems to be an upstream bug.

https://bugzilla.proxmox.com/show_bug.cgi?id=3516

Just changing ostype in /etc/pve/lxc/ID.conf to debian wasnt enough. The next problem seemed to be that inside the container the file /etc/os-release was missing (dont know why, after creating a new debian 11 container from the same image the file existed). But adding this file also didn't solve the problem. Here i gave up (it was just a testing container), since creating a new one worked.

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

4 participants