Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 2126
Multi Core | 15227
Full Test | https://browser.geekbench.com/v5/cpu/20618088
When you log in to your account, you could run the w command to see who is logged in and also the load averages.
If not too many people seem to be trying to run things, maybe you could exercise quite a few of the cores?
so maybe you could try using nice(1) sometime? I haven't used nice(1) for a while. I don't know how well nice(1) integrates with multi-threaded commands. Do you know?
I made you an account. Please try logging in with something like:
Please reread all the warnings in the OP. Please make sure to keep backups! Please let me know about all the stuff that isn't working.
Please monitor and please contribute some great content here in this thread! If you never post about what you are doing on the server, people might imagine that you are not using your account and no longer need it! 🤔
Rethinking my above posted reply to your question, maybe I have not given a sufficiently clear answer. That's because it's a shared server, so we have to be sensitive to what our neighbors are doing. For a short period of time, if you want to run something huge, and not too many others are around, then please go ahead! If you want to run something huge and for a long period of time, maybe post about it here in the thread before you go ahead?
Guys, apologies, there still is a bunch of stuff which needs to be installed. For example, Go and ndpresponder. Probably, in addition to Go and ndpresponder, there still remain more configuration steps with LXC. I need to carefully review what we did on the other server, make some notes, adjust for Alpine host --> Debian host, and try to finish up the configuration here. Everything will be fixed eventually. Please speak up as you notice things which need to be done.
@Not_Oles said:
Sure, definitely okay. It's been a pleasure talking with you here and by email. I hope we remain friends for a long time.
Thank you. And definitely.
By the way, I'm thinking of installing a web server. My default goto would be Apache. If you have a reason to want a different web server, I would appreciate it if you would tell me which one and why. Additionally, I suppose we could install Laravel, though I've not tried it and don't know hardly anything about it.
Apache is fine. As for laravel there is no need, it wont be wise to keep a "dev mode" laravel in "open" internet.
Following today's apt-get update, upgrade, and reboot, there are also new /etc/subuid and new /etc/subgid LXC configuration files which you can see.
Your starting subuid from /etc/subuid and your starting subgid from /etc/subgid should match the starting subuid and the starting subgid in your ~/.config/lxc/default.conf. So a change to your ~/.config/lxc/default.conf should be needed.
Please let me know about any issues by posting here in the thread.
@Not_Oles said: If you have time, could you please post the commands you ran to create the container? Thanks!
subenhon@sid:~$ #make sure the correct idmap is in the conf file
subenhon@sid:~$ cat $HOME/.config/lxc/default.conf
lxc.include = /etc/lxc/default.conf
lxc.idmap = u 0 165536 65536
lxc.idmap = g 0 165536 65536
subenhon@sid:~$ #create ubuntu container
subenhon@sid:~$ lxc-create -n ubuntu -f $HOME/.config/lxc/default.conf -t download -- --dist ubuntu --release focal --arch amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu focal amd64 (20230215_07:43) container.
To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
subenhon@sid:~$ # avoid apparmor error
subenhon@sid:~$ echo -e "lxc.apparmor.profile = unconfined\nlxc.apparmor.allow_nesting = 0\n" >> $HOME/.local/share/lxc/ubuntu/config
subenhon@sid:~$ #add x access to home before start the container or some error occurs
subenhon@sid:~$ chmod +x $HOME
subenhon@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
subenhon@sid:~$ #attach and set the password
subenhon@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# passwd
New password:
Retype new password:
passwd: password updated successfully
root@ubuntu:/# exit
exit
subenhon@sid:~$ # restart and login with the password
subenhon@sid:~$ lxc-stop -n ubuntu
subenhon@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu -F
Ubuntu 20.04.5 LTS ubuntu console
ubuntu login: root
Password:
Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 6.1.0-4-amd64 x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted byapplicable law.
root@ubuntu:~#
My recent several days have been invested in reading about configuring LXC, trying multiple different LXC configurations, and seeing multiple different and fascinating errors! I managed to follow @subenhon's steps, except that I didn't use the -F foreground option on restart. The result seems to be a working Ubuntu container with IPv4 but no IPv6 yet.
In order to get LXC really going on bare Debian, one needs at least a little understanding of LXC itself, cgroups, apparmor, systemd, networking, command line, the Debian package system and more. But, if I can (almost, sort of) do it with help from @subenhon, you certainly can do it too!
chronos@penguin:~/servers/hetzner/new2$ ssh [email protected] -p 42365
Linux sid 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 (2023-02-15) x86_64
Welcome to MetalVPS!
Last login: Thu Mar 2 16:29:17 2023 from 187.189.238.1
notoles@sid:~$ cat $HOME/.config/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.idmap = u 0 100000 65536
lxc.idmap = g 0 100000 65536
notoles@sid:~$ cat /etc/sub*id
notoles:100000:65536
subenhon:200000:65536
notoles:100000:65536
subenhon:200000:65536
notoles@sid:~$ lxc-create -n ubuntu -f $HOME/.config/lxc/default.conf -t download -- --dist ubuntu --release focal --arch amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu focal amd64 (20230228_07:44) container.
To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
notoles@sid:~$ grep apparmor $HOME/.local/share/lxc/ubuntu/config
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
notoles@sid:~$ echo -e "lxc.apparmor.profile = unconfined\nlxc.apparmor.allow_nesting = 0\n" >> $HOME/.local/share/lxc/ubuntu/config
notoles@sid:~$ grep apparmor $HOME/.local/share/lxc/ubuntu/config
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.apparmor.profile = unconfined
lxc.apparmor.allow_nesting = 0
notoles@sid:~$ # chmod +x $HOME
notoles@sid:~$ ls -l .. | grep notoles
drwx--x--x 6 notoles notoles 4096 Mar 2 01:18 notoles
notoles@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
Running scope as unit: my-unit.scope
notoles@sid:~$ # Attach and set the password
notoles@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# passwd
New password:
Retype new password:
passwd: password updated successfully
root@ubuntu:/# exit
exit
notoles@sid:~$ # restart and login with the password
notoles@sid:~$ lxc-stop -n ubuntu
notoles@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
Running scope as unit: my-unit.scope
notoles@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# ping -c 2 google.com
PING google.com (216.58.207.238) 56(84) bytes of data.
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=1 ttl=118 time=6.54 ms
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=2 ttl=118 time=6.67 ms
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 6.540/6.603/6.666/0.063 ms
root@ubuntu:/# ping6 -c 2 google.com
ping6: connect: Network is unreachable
root@ubuntu:/#
@Not_Oles said: Please think of your MetalVPS account as ephemeral! It might blow up! We or you might reinstall the Node! 🤦♂️
Hello!
I might wipe and reinstall this server. Maybe as soon as tomorrow. 😱 Does anyone who already has an account need anything on it? Does anyone who already has an account need temporary accommodations elsewhere? Thanks!
Somehow an EX101 suddenly appeared in my Hetzner Robot control panel! 💥 So this EX100 is scheduled for cancellation on April 4, 2023. 😢
Today is March 27 and March has 31 days. Sounds like that's what's left of today, plus March 28, 29, 30, and 31, plus April 1, 2, 3, and 4 that this EX100 can be used. Counting today, that's 9 days.
Does anybody want the entire server either for the 9 days or else as a transfer into their Hetzner account? I might be willing to reinstall it (again) for you or to give you access to Hetzner installimage so you could do the install yourself if you wish.
I probably want $30.33, but maybe not, depending on who / whatever. 🤩
Comments
Well,
nprocsaysThis thread's yabs says
and
When you log in to your account, you could run the
wcommand to see who is logged in and also the load averages.If not too many people seem to be trying to run things, maybe you could exercise quite a few of the cores?
Also, I just checked, and the server has
so maybe you could try using nice(1) sometime? I haven't used nice(1) for a while. I don't know how well nice(1) integrates with multi-threaded commands. Do you know?
I made you an account. Please try logging in with something like:
Please reread all the warnings in the OP. Please make sure to keep backups! Please let me know about all the stuff that isn't working.
Please monitor and please contribute some great content here in this thread! If you never post about what you are doing on the server, people might imagine that you are not using your account and no longer need it! 🤔
Have fun! 🎉
Best wishes!
Tom
Rethinking my above posted reply to your question, maybe I have not given a sufficiently clear answer. That's because it's a shared server, so we have to be sensitive to what our neighbors are doing. For a short period of time, if you want to run something huge, and not too many others are around, then please go ahead! If you want to run something huge and for a long period of time, maybe post about it here in the thread before you go ahead?
Is this answer a better answer?
Friendly greetings!
Guys, apologies, there still is a bunch of stuff which needs to be installed. For example, Go and ndpresponder. Probably, in addition to Go and ndpresponder, there still remain more configuration steps with LXC. I need to carefully review what we did on the other server, make some notes, adjust for Alpine host --> Debian host, and try to finish up the configuration here. Everything will be fixed eventually. Please speak up as you notice things which need to be done.
Thank you. And definitely.
Apache is fine. As for laravel there is no need, it wont be wise to keep a "dev mode" laravel in "open" internet.
Hello!
Following today's apt-get update, upgrade, and reboot, there are also new /etc/subuid and new /etc/subgid LXC configuration files which you can see.
Your starting subuid from /etc/subuid and your starting subgid from /etc/subgid should match the starting subuid and the starting subgid in your ~/.config/lxc/default.conf. So a change to your ~/.config/lxc/default.conf should be needed.
Please let me know about any issues by posting here in the thread.
Best!
Tom
@subenhon said:
My recent several days have been invested in reading about configuring LXC, trying multiple different LXC configurations, and seeing multiple different and fascinating errors!
I managed to follow @subenhon's steps, except that I didn't use the -F foreground option on restart. The result seems to be a working Ubuntu container with IPv4 but no IPv6 yet.
In order to get LXC really going on bare Debian, one needs at least a little understanding of LXC itself, cgroups, apparmor, systemd, networking, command line, the Debian package system and more. But, if I can (almost, sort of) do it with help from @subenhon, you certainly can do it too!
Hello!
I might wipe and reinstall this server. Maybe as soon as tomorrow. 😱 Does anyone who already has an account need anything on it? Does anyone who already has an account need temporary accommodations elsewhere? Thanks!
Best!
Tom
Hello!
Somehow an EX101 suddenly appeared in my Hetzner Robot control panel! 💥 So this EX100 is scheduled for cancellation on April 4, 2023. 😢
Today is March 27 and March has 31 days. Sounds like that's what's left of today, plus March 28, 29, 30, and 31, plus April 1, 2, 3, and 4 that this EX100 can be used. Counting today, that's 9 days.
Does anybody want the entire server either for the 9 days or else as a transfer into their Hetzner account? I might be willing to reinstall it (again) for you or to give you access to Hetzner installimage so you could do the install yourself if you wish.
I probably want $30.33, but maybe not, depending on who / whatever. 🤩
Friendly greetings!
Tom