I am following the howto below for installing proxmox on crostini
https://www.reddit.com/r/Crostini/wiki/howto/proxmox-ve-py/
Going through the steps when trying to install btrfs-progs apt returns the error below.
root@proxmox:~# apt install -y btrfs-progs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
duperemove
The following NEW packages will be installed:
btrfs-progs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 754 kB of archives.
After this operation, 4,591 kB of additional disk space will be used.
Ign:1 https://deb.debian.org/debian bookworm/main amd64 btrfs-progs amd64 6.2-1+deb12u1
Ign:1 https://deb.debian.org/debian bookworm/main amd64 btrfs-progs amd64 6.2-1+deb12u1
Ign:1 https://deb.debian.org/debian bookworm/main amd64 btrfs-progs amd64 6.2-1+deb12u1
Err:1 https://deb.debian.org/debian bookworm/main amd64 btrfs-progs amd64 6.2-1+deb12u1
Temporary failure resolving 'deb.debian.org'
E: Failed to fetch https://deb.debian.org/debian/pool/main/b/btrfs-progs/btrfs-progs\_6.2-1%2bdeb12u1\_amd64.deb Temporary failure resolving 'deb.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
root@proxmox:~#
It looks like the networking setup in the previous step of the script is preventing outbound network requests
fkhan@proxmox:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 172.20.20.254 icmp_seq=1 Destination Host Unreachable
From 172.20.20.254 icmp_seq=2 Destination Host Unreachable
From 172.20.20.254 icmp_seq=3 Destination Host Unreachable
From 172.20.20.254 icmp_seq=4 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4080ms
I tried rebooting the vm that did not help. Any other suggestions on what I should try?
I'm out and about for the next couple of hours and don't know if I'll have time later, but if you keep pinging me, I'll try to take a look. Just for reference, what is your normal network? IPv4 or IPv6?
My normal network is vanilla IPv4 with the default 192.168.x.x space.
Here is the network info returned by lxc info
1/3
2/3
3/3
In the container, what is the output of
ip netns exec ipv4 ip aand ofip netns exec ipv4 ip r?sudo systemctl restart systemd-networkd
network down after waking from sleep.
the script describes how crostini has a limited IPv4 allocation and reconfigures the network to IPv6
when I run sudo systemctl restart systemd-networkd the error below is returned
Googling the error returned that the service was symbolic linked to /dev/null.
I'm looking through the script now to see were that could be happening
Are you going through the steps one-by-one, or are you using the helper script that applies them automatically for you?
Are you using a completely fresh Crostini container, or are you using a container that you have previously used and modified?
Which version of Debian is running in your container? Google occasionally upgrades their Debian versions and it's possible that I haven't tested that particular configuration.
I just ran a test with whatever snapshot of Debian that I happened to have on my machine and using the automated script, and that particular combination seems to work. So, either you have a different version of Crostini and that is broken, or you made a mistake manually applying one of the steps. Also, it is possible that you broke your DHCP configuration if you have created and destroyed a lot of Crostini instances in the past. A powerwash would of course fix that, but there is a manual process to clean up your DHCP leases, if that proves to be the root cause. I can walk you through it, but it's a bit convoluted. So, let's try easier things first
Here is the version of debian installed
Both attempts were done on fresh containers created through the crosh vmc container command
The first attempt I tried to run the script and it failed when trying to install btrfs-progs because outbound network connections did not work
The second attempt I performed the steps by hand. They all worked except the step when creating the split-ipv4-ipv6 script through cat. With cat split-ipv4-ipv6 ended up truncated. When I created split-ipv4-ipv6 through vim it worked great.
Reviewing the first attempt that failed, the split-ipv4-ipv6 script is also truncated. Presumably this is why networking did not work.
I am currently trying to run the script again to see if I can duplicate the cat truncation.
Unfortunately, there seems to be two different errors on my 3rd attempt but they occur very early in the script.
The first error is when install_pve tries to open proxmox-ve.json
If I download proxmox-ve.json to the Downloads directory manually and relaunch the script the next error about an invalid option occurs.
I was able to run the script through the important parts on a different chromebook. It failed once the script started to try and create the first container because the ubuntu resource is not available and returns a 404.
After restarting the proxmox vm and realizing the ip address changes on reboot I was able to access the webpage on port 8006
thanks!
I have a question and a new problem.
Could I export my working proxmox container and import it on a different chromeos machine? The beginning part of the instructions is adjusting the security setting for the container. Do those setting persist in an export? Are there other steps I would need to do other than just lxc import <filename>
The problem I have now is going through the Integrate Container with Crostini the error below is thrown. What does the error mean by arch is missing?
I figured out why the 'arch' - internal error was happening. Creation of the 101.conf file was not working and resulted in an empty file.
The error was fixed by copying the preexisting 100.conf file I was able to execute the command pct start 101
apt install requires sudo.
[deleted]
[deleted]
[deleted]
yep, the script has the installation done as root
I repeated the installation by doing the instructions by hand using the human readable instructions
https://www.reddit.com/r/Crostini/wiki/howto/proxmox-ve/
and the networking now works and I was able to install btrfs-progs
So far the one deviation I had to do from the manual instructions is to create the split-ipv4-ipv6 in a text editor instead of cut&paste the cat instruction at the cli.
Unfortunately, with ChromeOS release 141 GUI support for multi-containers was removed. Assigning the port-forward for 8006 through the GUI is no longer possible because new containers is not populated in the dropdown.
I tried to open the site using garcon-url-handler and an error was returned
Yes, the removal of multi-containers is very annoying. This might be in preparation of the eventual merger with Android -- something that I already fear, as it is likely going to break a lot of other things.
But if you need to connect to one of the extra containers, you can do that by explicitly specifying their IP address. You can find your own IP address from inside the container with
ip netns exec ipv4 ip -4 -o a s dev eth0 | awk '{ sub(/\/.*/, "", $4); print $4 }'. Or you could just look in/etc/hosts. Part of what we did when installing PVE was to record the IP address that Crostini uses for us.Do you have a spare Linux machine you can use?
unfortunately no. only have chromeboxes and chromebooks available