Free Alpine Linux Shell Accounts

Not_Oles · February 2023

@Not_Oles said:
Hi guys! Sorry, but I just received an email from Hetrix saying that fmt ping monitor is down on IPv4 and on IPv6. Reported to @Cloudie. Will update when I know more. Thanks very much! Tom

Hetrix says its monitors are again receiving ping responses from fmt as of eight minutes ago.

terrorgen · February 2023

@Not_Oles said: @terrorgen Did you try it too?

Hey Tom, just trying it and looks like you need to add me to /etc/sub{u,g}id

Not_Oles · February 2023

@terrorgen said:

@Not_Oles said: @terrorgen Did you try it too?

Hey Tom, just trying it and looks like you need to add me to /etc/sub{u,g}id

Hi! Okay, added to /etc/sub*id and also to /etc/lxc/lxc-usernet. Please let me know if you need anything else. Have fun!

terrorgen · February 2023

@Not_Oles said:

@terrorgen said:

@Not_Oles said: @terrorgen Did you try it too?

Hey Tom, just trying it and looks like you need to add me to /etc/sub{u,g}id

Hi! Okay, added to /etc/sub*id and also to /etc/lxc/lxc-usernet. Please let me know if you need anything else. Have fun!

Thanks! However, I can't start my LXC container. Maybe it has something to do with lxcbr0?

Not_Oles · February 2023

Hi again @terrorgen!

Can you please take another look at how @subenhon got his container started?

If you did everything the same as @subenhon, are you seeing any errors? It can be helpful for seeing errors to use the "-F" a/k/a "--foreground" option to lxc-start.

I've been busy, so, unfortunately, I haven't tried this myself yet. But I will, eventually.

Thanks!

Tom

terrorgen · February 2023

I did, and it is stored at ~terrorgen/log if you want to take a peek.

To save everyone's time, I think it is because of this:

lxc-start nixos 20230220204723.613 ERROR    start - ../src/lxc/start.c:lxc_spawn:1795 - Failed to setup cgroup limits for container "nixos"

Does the lack of systemd in Alpine contribute to this? Cause I also saw some TRACE messages related to systemd not being found.

Not_Oles · February 2023

There are many interesting entries in those logs!

I forgot to initialize the bridge when I last rebooted. I have to set the bridge so it starts automagically.

Want to try starting your container again, please?

terrorgen · February 2023

And it's still not working for me to get NixOS run on LXC.

I tried downloading a standard debian and Ubuntu templates but was unsuccessful as well.
Must be the configuration.

Not_Oles · February 2023

It seems that the LXC containers might be working on this server! Thanks to @yoursunny for helping a lot to prepare the way! Thanks to @subenhon for blazing the trail!

@subenhon said:
@Not_Oles ,Here is how I create the Lxc container.

~ $ cat $HOME/.config/lxc/default.conf
lxc.include = /etc/lxc/default.conf
lxc.idmap = u 0 1022000000 65536
lxc.idmap = g 0 1022000000 65536
~ $ lxc-create -n alpine -f $HOME/.config/lxc/default.conf -t download -- --dist alpine --release 3.17 --arch amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Alpinelinux 3.17 x86_64 (20230123_20:03) container.
~ $# change container root password and network setting frome dhcp to manual
~ $ lxc-attach -n alpine
/ # passwd
Changing password for root
New password: 
Retype password: 
passwd: password for root changed by root
/ # exit
~ $ # container ip config  
~ $ echo -e "lxc.net.0.ipv4.address = 192.168.188.58/24\nlxc.net.0.ipv4.gateway = auto" >> $HOME/.local/share/lxc/alpine/config
~ $ echo -e "lxc.net.0.ipv6.address = 2602:fba1:999:1c00:58::/64\nlxc.net.0.ipv6.gateway = auto" >> $HOME/.local/share/lxc/alpine/config
~ $ #restart container
~ $ lxc-stop -n alpine
~ $ lxc-start -n alpine
~ $ lxc-console -n alpine
Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
Welcome to Alpine Linux 3.17
Kernel 6.1.8-0-lts on an x86_64 (/dev/tty1)

alpine login: root
Password: 
Welcome to Alpine!

The Alpine Wiki contains a large amount of how-to guides and general
information about administrating Alpine systems.
See <https://wiki.alpinelinux.org/>.

You can setup the system with the command: setup-alpine

You may change this message by editing /etc/motd.

alpine:~# #add nameserver
alpine:~# echo -e "nameserver 1.1.1.1\nnameserver 2001:470:20::2\n" >> /etc/resolv.conf
alpine:~# ping -4 google.com
PING google.com (142.251.46.238): 56 data bytes
64 bytes from 142.251.46.238: seq=0 ttl=119 time=1.691 ms
64 bytes from 142.251.46.238: seq=1 ttl=119 time=1.604 ms
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.604/1.647/1.691 ms
alpine:~# ping -6 google.com
PING google.com (2607:f8b0:4005:80b::200e): 56 data bytes
64 bytes from 2607:f8b0:4005:80b::200e: seq=0 ttl=117 time=50.880 ms
64 bytes from 2607:f8b0:4005:80b::200e: seq=1 ttl=117 time=1.773 ms

There are some small differences between my procedure and @subenhon's procedure. In particular, I don't understand why @subenhon seemed to get working autoconfigured IPv4 out of the box and I perhaps didn't.

Here is my transcript.

# See @subenhon's post at
# https://lowendspirit.com/discussion/comment/127589/#Comment_127589
fmt:~/.config/lxc$ cat default.conf 
lxc.include = /etc/lxc/default.conf
lxc.idmap = u 0 1000000000 65536
lxc.idmap = g 0 1000000000 65536
fmt:~/.config/lxc$ cd
fmt:~$ lxc-create -n alpine -f $HOME/.config/lxc/default.conf -t download -- --dist alpin
e --release 3.17 --arch amd64
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Alpinelinux 3.17 x86_64 (20230220_13:11) container.
fmt:~$ lxc-ls
alpine 
fmt:~$ lxc-attach -n alpine
lxc-attach: alpine: ../src/lxc/attach.c: get_attach_context: 406 Connection refused - Failed to get init pid
lxc-attach: alpine: ../src/lxc/attach.c: lxc_attach: 1470 Connection refused - Failed to get attach context
fmt:~$ lxc-start -n alpine
fmt:~$ lxc-attach -n alpine
/ # cd
/bin/ash: cd: can't cd to /home/notoles: No such file or directory
/ # whoami
root
/ # cd root
~ # pwd
/root
~ # passwd
Changing password for root
New password: 
Retype password: 
passwd: password for root changed by root
~ # echo -e "nameserver 1.1.1.1\nnameserver 2001:470:20::2\n" >> /etc/resolv.conf
~ # ping -4 -c 2 google.com
ping: bad address 'google.com'
~ # exit
fmt:~$ echo -e "lxc.net.0.ipv4.address = 192.168.188.10/24\nlxc.net.0.ipv4.gateway = auto
" >> $HOME/.local/share/lxc/alpine/config
fmt:~$ echo -e "lxc.net.0.ipv6.address = 2602:fba1:999:1c00:10::/64\nlxc.net.0.ipv6.gatew
ay = auto" >> $HOME/.local/share/lxc/alpine/config
fmt:~$ cat -n $HOME/.local/share/lxc/alpine/config
     1  # Template used to create this container: /usr/share/lxc/templates/lxc-download
     2  # Parameters passed to the template: --dist alpine --release 3.17 --arch amd64
     3  # For additional config options, please look at lxc.container.conf(5)
     4
     5  # Uncomment the following line to support nesting containers:
     6  #lxc.include = /usr/share/lxc/config/nesting.conf
     7  # (Be aware this has security implications)
     8
     9
    10  # Distribution configuration
    11  lxc.include = /usr/share/lxc/config/common.conf
    12  lxc.include = /usr/share/lxc/config/userns.conf
    13  lxc.arch = linux64
    14
    15  # Container specific configuration
    16  lxc.include = /etc/lxc/default.conf
    17  lxc.idmap = u 0 1000000000 65536
    18  lxc.idmap = g 0 1000000000 65536
    19  lxc.rootfs.path = dir:/home/notoles/.local/share/lxc/alpine/rootfs
    20  lxc.uts.name = alpine
    21
    22  # Network configuration
    23  lxc.net.0.ipv4.address = 192.168.188.10/24
    24  lxc.net.0.ipv4.gateway = auto
    25  lxc.net.0.ipv6.address = 2602:fba1:999:1c00:10::/64
    26  lxc.net.0.ipv6.gateway = auto
fmt:~$ lxc-stop -n alpine
fmt:~$ lxc-start -n alpine
fmt:~$ lxc-attach -n alpine
/ # ping -4 -c 2 google.com
PING google.com (142.251.32.46): 56 data bytes
ping: sendto: Network unreachable
/ # ping -6 -c 2 google.com
PING google.com (2607:f8b0:4005:811::200e): 56 data bytes
64 bytes from 2607:f8b0:4005:811::200e: seq=0 ttl=119 time=1.602 ms
64 bytes from 2607:f8b0:4005:811::200e: seq=1 ttl=119 time=1.561 ms

--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.561/1.581/1.602 ms
/ # / # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0@if35: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 00:16:3e:24:60:3e brd ff:ff:ff:ff:ff:ff
/ # ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if35: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 00:16:3e:24:60:3e brd ff:ff:ff:ff:ff:ff
    inet6 2602:fba1:999:1c00:10::/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fe24:603e/64 scope link 
       valid_lft forever preferred_lft forever
/ # ip address add 192.168.188.10/24 dev eth0
/ # ip route add 192.168.188.1 dev eth0
/ # ip route add default via 192.168.188.1 dev eth0
/ # ping -4 -c 2 google.com
PING google.com (142.251.46.238): 56 data bytes
64 bytes from 142.251.46.238: seq=0 ttl=119 time=1.552 ms
64 bytes from 142.251.46.238: seq=1 ttl=119 time=1.534 ms

--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.534/1.543/1.552 ms
/ # wget -qO- ipv4.icanhazip.com
23.134.88.227
/ # vi ipv4-up.sh
/ # cat -n ipv4-up.sh 
     1  ip address add 192.168.188.10/24 dev eth0
     2  ip route add 192.168.188.1 dev eth0
     3  ip route add default via 192.168.188.1 dev eth0
/ #

yoursunny · February 2023

@terrorgen said:
Does the lack of systemd in Alpine contribute to this?

Yes, systemd won't start in LXC container due to lack of cgroups.

See my test report:
https://lowendspirit.com/discussion/comment/125271/#Comment_125271
Look at lxc.init.cmd line under "these are typed by user".

Not_Oles · February 2023

@yoursunny said:

@terrorgen said:
Does the lack of systemd in Alpine contribute to this?

Yes, systemd won't start in LXC container due to lack of cgroups.

See my test report:
https://lowendspirit.com/discussion/comment/125271/#Comment_125271
Look at lxc.init.cmd line under "these are typed by user".

Hi @yoursunny! We were talking about setting your container quantity in /etc/lxc/lxc-usernet. Is it time to raise your quantity now? I forget how many you wanted, so can you remind me, please? Thanks!

Not_Oles · February 2023

@terrorgen said: I tried downloading a standard debian and Ubuntu templates but was unsuccessful as well.

Sorry to hear. I should try these as well. Do you have any info about what went wrong? Any error messages? Thanks!

subenhon · February 2023

@Not_Oles said: There are some small differences between my procedure and @subenhon's procedure. In particular, I don't understand why @subenhon seemed to get working autoconfigured IPv4 out of the box and I perhaps didn't.

@Not_Oles I change the network type from dhcp to manual when attach to the container , maybe you missed this part.

~ $# change container root password and network setting from dhcp to manual
~ $ lxc-attach -n alpine
/ # passwd
Changing password for root
New password:
Retype password:
passwd: password for root changed by root

alpine:~# cat /etc/network/interfaces
auto eth0
iface eth0 inet manual
hostname $(hostname)

terrorgen · February 2023

@yoursunny said:

@terrorgen said:
Does the lack of systemd in Alpine contribute to this?

Yes, systemd won't start in LXC container due to lack of cgroups.

According to https://wiki.alpinelinux.org/wiki/LXC, cgroup can be enabled with rc-update add cgroups

Worth a try, @Not_Oles?

Not_Oles · February 2023

Hi again! Here are some shenanigans with Debian.

fmt:~$ pwd
/home/notoles
fmt:~$ whoami
notoles
fmt:~$ lxc-create -n debian -f $HOME/.config/lxc/default.conf -t download -- --dist debia
n --release sid --arch amd64
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
../src/lxc/cmd/lxc_usernsexec.c: 64: opentty - Permission denied - Failed to open tty
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created a Debian sid amd64 (20230220_05:24) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
fmt:~$ echo -e "lxc.net.0.ipv4.address = 192.168.188.11/24\nlxc.net.0.ipv4.gateway = auto
> " >> $HOME/.local/share/lxc/debian/config
fmt:~$ echo -e "lxc.net.0.ipv6.address = 2602:fba1:999:1c00:11::/64\nlxc.net.0.ipv6.gatew
> ay = auto" >> $HOME/.local/share/lxc/debian/config
fmt:~$ cat -n $HOME/.local/share/lxc/debian/config
     1  # Template used to create this container: /usr/share/lxc/templates/lxc-download
     2  # Parameters passed to the template: --dist debian --release sid --arch amd64
     3  # For additional config options, please look at lxc.container.conf(5)
     4
     5  # Uncomment the following line to support nesting containers:
     6  #lxc.include = /usr/share/lxc/config/nesting.conf
     7  # (Be aware this has security implications)
     8
     9
    10  # Distribution configuration
    11  lxc.include = /usr/share/lxc/config/common.conf
    12  lxc.include = /usr/share/lxc/config/userns.conf
    13  lxc.arch = linux64
    14
    15  # Container specific configuration
    16  lxc.include = /etc/lxc/default.conf
    17  lxc.idmap = u 0 1000000000 65536
    18  lxc.idmap = g 0 1000000000 65536
    19  lxc.rootfs.path = dir:/home/notoles/.local/share/lxc/debian/rootfs
    20  lxc.uts.name = debian
    21
    22  # Network configuration
    23  lxc.net.0.ipv4.address = 192.168.188.11/24
    24  lxc.net.0.ipv4.gateway = 192.168.188.1
    25
    26  lxc.net.0.ipv6.address = 2602:fba1:999:1c00:11::/64
    27  lxc.net.0.ipv6.gateway = 2602:fba1:999:1c00:11::
fmt:~$ lxc-start -F -n debian
Failed to find module 'autofs4'
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
fmt:~$ # https://lowendspirit.com/discussion/comment/125271/#Comment_125271
fmt:~/.local/share/lxc/debian$ echo lxc.init.cmd = /bin/bash >> config 
fmt:~/.local/share/lxc/debian$ cd
fmt:~$ lxc-start -F debian
root@debian:/# cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
root@debian:/# ping -c 2 google.com
ping: google.com: Temporary failure in name resolution
root@debian:/# cd etc
root@debian:/etc# ls -l 
total 392
  [ . . . ]
lrwxrwxrwx 1 root root      37 Feb 20 05:29 resolv.conf -> /run/systemd/resolve/stub-resolv.conf
  [ . . . ]
root@debian:/etc# rm resolv.conf 
root@debian:/etc# echo -e "nameserver 1.1.1.1\nnameserver 2001:470:20::2\n" >> /etc/resolv.conf
root@debian:/etc# cd /root
root@debian:/root# ping -c 2 google.com
PING google.com(sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e)) 56 data bytes
64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=1 ttl=117 time=66.0 ms
64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=2 ttl=117 time=1.82 ms

--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 1.816/33.907/65.998/32.091 ms
root@debian:/root# ping -4 -c 2 google.com
PING  (142.251.32.46) 56(84) bytes of data.
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=1 ttl=119 time=1.64 ms
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=2 ttl=119 time=1.32 ms

---  ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.318/1.478/1.638/0.160 ms
root@debian:/root# exit
exit
fmt:~$ lxc-stop -n debian
lxc-stop: debian: ../src/lxc/tools/lxc_stop.c: main: 168 debian is not running
fmt:~$

Not_Oles · February 2023

Hi @terrorgen!

@terrorgen said: According to https://wiki.alpinelinux.org/wiki/LXC, cgroup can be enabled with rc-update add cgroups

Worth a try, @Not_Oles?

Already done, I think. Please take a look at the seond to last entry under Default runlevel.

fmt:~$ rc-status -a 
Runlevel: nonetwork
Runlevel: sysinit
 devfs                                                                      [  started  ]
 dmesg                                                                      [  started  ]
 mdev                                                                       [  started  ]
 hwdrivers                                                                  [  started  ]
Runlevel: default
 vnstatd                                                                    [  started  ]
 nix-daemon                                                                 [  started  ]
 acpid                                                                      [  started  ]
 crond                                                                      [  started  ]
 sshd                                                                       [  started  ]
 cgroups                                                                    [  started  ]    <== Here! 
 chronyd                                                                    [  started  ]
Runlevel: boot
 modules                                                                    [  started  ]
 hwclock                                                                    [  started  ]
 swap                                                                       [  started  ]
 utmp-prepare                                                               [  started  ]
 sysctl                                                                     [  started  ]
 bootmisc                                                                   [  started  ]
 utmpd                                                                      [  started  ]
 seedrng                                                                    [  started  ]
 btmpd                                                                      [  started  ]
 loadkmap                                                                   [  started  ]
 wtmpd                                                                      [  started  ]
 utmp-init                                                                  [  started  ]
 hostname                                                                   [  started  ]
 syslog                                                                     [  started  ]
 networking                                                                 [  started  ]
Runlevel: shutdown
 killprocs                                                                  [  stopped  ]
 savecache                                                                  [  stopped  ]
 mount-ro                                                                   [  stopped  ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
 sysfs                                                                      [  started  ]
 fsck                                                                       [  started  ]
 root                                                                       [  started  ]
 localmount                                                                 [  started  ]
Dynamic Runlevel: manual
fmt:~$

Not_Oles · February 2023

It looks like I can get a persistent Debian container by using tmux.

fmt:~$ tmux
fmt:~$ lxc-start -F -n debian
root@debian:/#

Inside the container, enter Ctrl-b followed by d to detach from the container and return to the host while leaving the container running.

On the host, enter "tmux attach" to reattach to the container which is still running inside tmux.

To stop the container from inside the container (which is inside tmux), enter "exit." To close tmux, enter "exit" again.

terrorgen · February 2023

Looks like bash is PID1 in your container?

terrorgen · February 2023

Btw, FMT not pingable from my end.

Not_Oles · February 2023

@subenhon said: @Not_Oles I change the network type from dhcp to manual when attach to the container , maybe you missed this part.

Yup. Thanks for the reminder! Much appreciated!

Not_Oles · February 2023

@terrorgen said:
Btw, FMT not pingable from my end.

Yeah, work in the datacenter. Downtime was not expected. But it nevertheless seems to have arrived.

You can check

IPv4
IPv6

Not_Oles · February 2023

@terrorgen said:
Looks like bash is PID1 in your container?

Yeah, I think so, as a way to fix certain errors noted above which are, for easy reference, repeated here:

@Not_Oles said:

fmt:~$ lxc-start -F -n debian
Failed to find module 'autofs4'
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
fmt:~$ # https://lowendspirit.com/discussion/comment/125271/#Comment_125271
fmt:~/.local/share/lxc/debian$ echo lxc.init.cmd = /bin/bash >> config 
fmt:~/.local/share/lxc/debian$ cd
fmt:~$ lxc-start -F -n debian
root@debian:/#

Now the questions are (1) why did the errors happen, and (2) can we find a configuration that prevents them from happening?

yoursunny · February 2023

@Not_Oles said:
Hi @yoursunny! We were talking about setting your container quantity in /etc/lxc/lxc-usernet. Is it time to raise your quantity now? I forget how many you wanted, so can you remind me, please? Thanks!

I typically configure "100" in lxc-usernet so it's never a limitation.
There's really no need to place a limit here, because a user can have practically any number of containers by making creating nested containers that isn't subject to this limit.

terrorgen · February 2023

@Not_Oles said:

@terrorgen said:
Looks like bash is PID1 in your container?

Yeah, I think so, as a way to fix certain errors noted above which are, for easy reference, repeated here:

@Not_Oles said:
fmt:~$ lxc-start -F -n debian
Failed to find module 'autofs4'
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
fmt:~$ # https://lowendspirit.com/discussion/comment/125271/#Comment_125271
fmt:~/.local/share/lxc/debian$ echo lxc.init.cmd = /bin/bash >> config 
fmt:~/.local/share/lxc/debian$ cd
fmt:~$ lxc-start -F -n debian
root@debian:/# 
Now the questions are (1) why did the errors happen, and (2) can we find a configuration that prevents them from happening?

I got similar errors on my NixOS container about autofs and cgroup and PID1 refusing to proceed further. Looks like a systemd issue now.

terrorgen · February 2023

Oh just found this from https://wiki.alpinelinux.org/wiki/LXD:

If you plan to run systemd based Linux distributions (Debian, Ubuntu, etc.), add this to /etc/conf.d/lxc:

systemd_container=yes
and enable both lxc and lxd to start at boot:

 rc-update add lxc
 rc-update add lxd
 rc-update add lxcfs

If you have problems, try to enable dbus:

rc-update add dbus
Reboot and lxd should be working.

Not_Oles · February 2023

HI! The server seems to be back up, and services are restarted. If anybody has any issues, please let me know. Thanks!

root@debian:/# date -u                                                                  
Tue Feb 21 22:23:21 UTC 2023
root@debian:/# ping6 -c 2 google.com
PING google.com(nuq04s43-in-x0e.1e100.net (2607:f8b0:4005:810::200e)) 56 data bytes
64 bytes from nuq04s43-in-x0e.1e100.net (2607:f8b0:4005:810::200e): icmp_seq=1 ttl=119 time=59.7 ms
64 bytes from nuq04s43-in-x0e.1e100.net (2607:f8b0:4005:810::200e): icmp_seq=2 ttl=119 time=1.76 ms

--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.757/30.729/59.702/28.972 ms
root@debian:/# ping -4 -c 2 google.com
PING  (142.251.46.238) 56(84) bytes of data.
64 bytes from sfo03s27-in-f14.1e100.net (142.251.46.238): icmp_seq=1 ttl=119 time=1.53 ms
64 bytes from sfo03s27-in-f14.1e100.net (142.251.46.238): icmp_seq=2 ttl=119 time=1.61 ms

---  ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 1.534/1.572/1.610/0.038 ms
root@debian:/#

Not_Oles · February 2023

Inside LXC Container Described Above

root@debian:/# curl -sL yabs.sh | bash
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2022-12-29                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Tue Feb 21 22:43:59 UTC 2023

Basic System Information:
---------------------------------
Uptime     : 0 days, 9 hours, 44 minutes
Processor  : Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz
CPU cores  : 24 @ 1837.301 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 62.8 GiB
Swap       : 4.0 GiB
Disk       : 453.3 GiB
Distro     : Debian GNU/Linux bookworm/sid
Kernel     : 6.1.12-0-lts

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 71.81 MB/s   (17.9k) | 119.56 MB/s   (1.8k)
Write      | 72.00 MB/s   (18.0k) | 120.19 MB/s   (1.8k)
Total      | 143.82 MB/s  (35.9k) | 239.75 MB/s   (3.7k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 119.06 MB/s    (232) | 129.29 MB/s    (126)
Write      | 125.39 MB/s    (244) | 137.90 MB/s    (134)
Total      | 244.46 MB/s    (476) | 267.20 MB/s    (260)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 854 Mbits/sec   | 210 Mbits/sec   | 143 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 142 ms         
NovoServe       | North Holland, NL (40G)   | 651 Mbits/sec   | 544 Mbits/sec   | 137 ms         
Uztelecom       | Tashkent, UZ (10G)        | busy            | 43.2 Mbits/sec  | 244 ms         
Clouvider       | NYC, NY, US (10G)         | 713 Mbits/sec   | 124 Mbits/sec   | 70.4 ms        
Clouvider       | Dallas, TX, US (10G)      | 627 Mbits/sec   | 633 Mbits/sec   | 41.8 ms        
Clouvider       | Los Angeles, CA, US (10G) | 785 Mbits/sec   | 645 Mbits/sec   | 26.9 ms        

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 845 Mbits/sec   | 297 Mbits/sec   | 130 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 141 ms         
NovoServe       | North Holland, NL (40G)   | 836 Mbits/sec   | 586 Mbits/sec   | 136 ms         
Uztelecom       | Tashkent, UZ (10G)        | 722 Mbits/sec   | 242 Mbits/sec   | 220 ms         
Clouvider       | NYC, NY, US (10G)         | 888 Mbits/sec   | 613 Mbits/sec   | 69.9 ms        
Clouvider       | Dallas, TX, US (10G)      | 920 Mbits/sec   | 795 Mbits/sec   | 41.9 ms        
Clouvider       | Los Angeles, CA, US (10G) | 933 Mbits/sec   | 902 Mbits/sec   | 11.1 ms  

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 561                           
Multi Core      | 7252                          
Full Test       | https://browser.geekbench.com/v5/cpu/20708994

YABS completed in 12 min 37 sec
root@debian:/#

On The Bare Metal Server Node

fmt:~# curl -sL yabs.sh | bash
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2022-12-29                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Tue Feb 21 23:00:46 UTC 2023
bash: line 29: locale: command not found

Warning: locale 'C' not detected. Test outputs may not be parsed correctly.

Basic System Information:
---------------------------------
Uptime     : 0 days, 10 hours, 1 minutes
Processor  : Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz
CPU cores  : 24 @ 1800.000 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 62.8 GiB
Swap       : 4.0 GiB
Disk       : 
Distro     : Alpine Linux edge
Kernel     : 6.1.12-0-lts

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 71.90 MB/s   (17.9k) | 119.49 MB/s   (1.8k)
Write      | 72.09 MB/s   (18.0k) | 120.12 MB/s   (1.8k)
Total      | 143.99 MB/s  (35.9k) | 239.61 MB/s   (3.7k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 119.04 MB/s    (232) | 129.66 MB/s    (126)
Write      | 125.37 MB/s    (244) | 138.29 MB/s    (135)
Total      | 244.42 MB/s    (476) | 267.95 MB/s    (261)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 333 Mbits/sec   | 188 Mbits/sec   | 131.566 ms     
Scaleway        | Paris, FR (10G)           | busy            | 446 Mbits/sec   | 142.122 ms     
NovoServe       | North Holland, NL (40G)   | 231 Mbits/sec   | 554 Mbits/sec   | 136.405 ms     
Uztelecom       | Tashkent, UZ (10G)        | 698 Mbits/sec   | 149 Mbits/sec   | 220.116 ms     
Clouvider       | NYC, NY, US (10G)         | 327 Mbits/sec   | 266 Mbits/sec   | 70.053 ms      
Clouvider       | Dallas, TX, US (10G)      | busy            | 613 Mbits/sec   | 41.824 ms      
Clouvider       | Los Angeles, CA, US (10G) | 672 Mbits/sec   | 793 Mbits/sec   | 11.033 ms      

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 829 Mbits/sec   | 309 Mbits/sec   | 131.664 ms     
Scaleway        | Paris, FR (10G)           | 838 Mbits/sec   | 307 Mbits/sec   | 136.759 ms     
NovoServe       | North Holland, NL (40G)   | 837 Mbits/sec   | 585 Mbits/sec   | 136.204 ms     
Uztelecom       | Tashkent, UZ (10G)        | 644 Mbits/sec   | 276 Mbits/sec   | 219.915 ms     
Clouvider       | NYC, NY, US (10G)         | 888 Mbits/sec   | 681 Mbits/sec   | 69.913 ms      
Clouvider       | Dallas, TX, US (10G)      | 907 Mbits/sec   | 709 Mbits/sec   | 41.799 ms      
Clouvider       | Los Angeles, CA, US (10G) | 831 Mbits/sec   | 922 Mbits/sec   | 11.090 ms      

Geekbench 5 test failed. Run manually to determine cause.

YABS completed in 7 min 35 sec
fmt:~# 

fmt:~/Geekbench-5.4.6-Linux# ./geekbench_x86_64 
Geekbench 5.4.6 Tryout : https://www.geekbench.com/
  [ . . . ]
Running Gathering system information
Segmentation fault
fmt:~/Geekbench-5.4.6-Linux#

superyuluo · February 2023

I would also love to try one of the accounts. Thank you!!

Not_Oles · February 2023

Hi @superyuluo!

Welcome to LES! I hope you enjoy your time here!

Since you have a new account, I am sure that everyone here would enjoy meeting you. Would you please introduce yourself? Please tell us

who and where you are,
about your Linux experience, and
what you plan to do on the server.

Also, to give you an account, we need your ed25519 ssh public key. Would you please post your key or a link to it?

I am looking forward to having you join us on the server!

Best!

Tom

terrorgen · February 2023

Looks like I am still not able to start my container.

@terrorgen said:
Oh just found this from https://wiki.alpinelinux.org/wiki/LXD:

If you plan to run systemd based Linux distributions (Debian, Ubuntu, etc.), add this to /etc/conf.d/lxc:

systemd_container=yes
and enable both lxc and lxd to start at boot:
 rc-update add lxc
 rc-update add lxd
 rc-update add lxcfs
If you have problems, try to enable dbus:

rc-update add dbus
Reboot and lxd should be working.

@Not_Oles you'll have to do this ☺️

Free Alpine Linux Shell Accounts

Comments

Inside LXC Container Described Above

On The Bare Metal Server Node