microLXC Public Test

17810121315

Comments

  • NeoonNeoon OG
    edited January 2024

    @ElonBezos said:

    @Neoon said:

    Looks more like a issue related to SSH for some reason.

    i'll look further in to this

    Tokyo no idea, we got 2 Nodes, you have to be more precise.

    it said tyo only, the other tyo equinix seems fine for me

    anyway unable to ssh is not a big deal for me since i can access them from the portal

    Well, seems to be the same issue, SSH not listening.
    Not a forwarding issue or anything, since the rules are in place and IPv6 returns the same result.

    However, I can't replicate that, so no idea yet.

  • Will do a quick reboot on Singapore and Groningen on Friday, at around 21:00 UTC.
    More Stock should be available afterwards.

  • 594c-620d-842c-7996

  • Islamabad is now available, Native IPv6 however only a /70 and depending on version and distro, manual configuration might be required.

    Thanks to https://virtury.com

    Currently 3 Packages are available.

    • 1x Core (25%), 64MB, 1.3GB ZFS, 100GB @ 100Mbit
    • 1x Core (50%), 128MB, 2.0GB ZFS, 200GB @ 100Mbit
    • 1x Core (50%), 256MB, 2.5GB ZFS, 200GB @ 100Mbit
  • May I apply for a tiny R0 VPS?

  • NeoonNeoon OG
    edited February 2024

    RO gets migrated from E5 to Xeon Gold in 1 hour ish. Thanks @host_c / https://www.host-c.com/
    NL is next on the list, but no ETA, gonna be EYPC though.

  • @ElonBezos said:

    @Neoon said:

    Looks more like a issue related to SSH for some reason.

    i'll look further in to this

    Tokyo no idea, we got 2 Nodes, you have to be more precise.

    it said tyo only, the other tyo equinix seems fine for me

    anyway unable to ssh is not a big deal for me since i can access them from the portal

    Was that 64MB?
    Looks like an issue due to low memory and a combination of what OS you choose to install.

  • Debian/Devuan has issues with 64MB, so I disabled it again.
    It doesn't work reliable enough.

  • Are you aware of IPv6 issues in PK? Seems like their subnet disappeared from the DFZ: https://bgp.tools/prefix/2001:df2:d40::/48

    dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/

  • NeoonNeoon OG
    edited February 2024

    @Brueggus said:
    Are you aware of IPv6 issues in PK? Seems like their subnet disappeared from the DFZ: https://bgp.tools/prefix/2001:df2:d40::/48

    I wasn't, didn't check my email box, yet.
    Will Ticket him later, at some point we should have a /48 Prefix ready in PK, no ETA though, waiting since 1 week for him to announce it.
    Thanks to @host_c for providing the Prefix, since I don't have my own allocation or ASN yet.

  • @Neoon said: allocation or ASN yet.

    I think we can help with that, PM me when you are interested.

    PS: I did send you something via PM by the way :)

    Host-C | Storage by Design | AS211462

    “If it can’t guarantee behavior under load, it doesn’t belong in production.”

  • @Brueggus said:
    Are you aware of IPv6 issues in PK? Seems like their subnet disappeared from the DFZ: https://bgp.tools/prefix/2001:df2:d40::/48

    They replied but no fix yet.

  • @Neoon said:

    @Brueggus said:
    Are you aware of IPv6 issues in PK? Seems like their subnet disappeared from the DFZ: https://bgp.tools/prefix/2001:df2:d40::/48

    They replied but no fix yet.

    The Prefix used in PK is back on the routing table, however no reply yet.

  • Helsinki is now available, No IPv6 however, plan was running a wg tunnel back to Norway, however routing was not feasible.
    Right now its without IPv6 and probably will stay this way, local brokers are available though.

    Thanks to https://pulsedmedia.com

    Currently 4 Packages are available.

    • 1x Core (100%), 512MB, 10GB ZFS Raid 1, 1TB @ 200Mbit
    • 1x Core (100%), 512MB, 50GB ZFS Raid 1, 1TB @ 200Mbit, Limited to 5
    • 1x Core (100%), 1024MB, 25GB ZFS Raid 1, 1TB @ 200Mbit
    • 1x Core (100%), 1024MB, 50GB ZFS Raid 1, 1TB @ 200Mbit, Limited to 5

    This Location will be KVM only for now, since this is our first machine with Debian, I don't have a live kernel patching solution yet so no LXC, expect a reboot though every now and then, will be announced here.
    Because we don't have smoler packages available, the is currently a 50% discount off the memory usage, so if you get the 512MB package it will be calculated as 256MB and so on until the Node is about half full.

  • NeoonNeoon OG
    edited March 2024

    Maintenance announcement for New Zealand.
    Expect about 60 minutes downtime at Wednesday the 14th of March at 12:30AM NZDT / 11:30AM GMT
    Due to scheduled hardware upgrades.

  • Restocked Helsinki.

  • Maintenance Announcement
    I have to carry out some changes on the backend, this will make the backend unavailable for roughly 1 hour or less.
    Running machines are not affected, however no tasks or deployments can be done.
    Should be done next week, Friday, 15th of March, at around 20:00 GMT.

  • NeoonNeoon OG
    edited March 2024

    Got SPICE working.
    You should be able to install any OS with netboot.xyz on KVM.

  • Spice is now available along with an option under Settings to boot from ISO (netboot.xyz).
    That will set the boot priority up and mount the ISO.

    I added empty KVM's too (BYOOS), so we can offer 256MB KVM's again.
    Debian 12 isn't going to boot or run on these, some other operating systems might run though.

    The 256MB KVM Package is only available in Finland right now, if there is any use, I can add it to Norway and Dronten too.

  • I added a 384MB KVM too on Helsinki.
    Since 256MB seems to barely work with netboot.xyz to get any installer up.

    I will add more iso's and an option to switch iso's later.

  • NeoonNeoon OG
    edited March 2024

    /48 IPv6 for PK is on the way, should be available in the next few days.
    Took a bit longer than expected.

    Thanks again to @host_c / https://www.host-c.com

    No ETA for Tokyo though.
    The containers on Tokyo have been restarted today accidentally, I needed to replace a certificate however I did a restart instead of a reload, hence the reboot.

  • nice to see Helsinki
    i gotta read how to apply for this first.

    <3 to Neoon

  • edited March 2024

    if u still have room:

    3077-1c51-1101-2aa1

  • @ehab said:
    if u still have room:

    3077-1c51-1101-2aa1

    Always.

  • Finland currently has network issues, I had to reboot the node.
    Out of Stock for now.

    As soon as I know more, I will post it here.

  • @Neoon said:
    Finland currently has network issues, I had to reboot the node.
    Out of Stock for now.

    As soon as I know more, I will post it here.

    The issue has been found, a switch gone bad.
    Its gonna be replaced next week, if it gets unstable again, earlier.

    Stock has been enabled again.

  • @Neoon said:

    @Neoon said:
    Finland currently has network issues, I had to reboot the node.
    Out of Stock for now.

    As soon as I know more, I will post it here.

    The issue has been found, a switch gone bad.
    Its gonna be replaced next week, if it gets unstable again, earlier.

    Stock has been enabled again.

    Switch has been replaced.

  • host_chost_c Provider

    @Neoon said: Switch has been replaced.

    yeeeeee!

    Host-C | Storage by Design | AS211462

    “If it can’t guarantee behavior under load, it doesn’t belong in production.”

  • Restocked Finland.

  • openSUSE image has been removed, since the official Imageserver does not build it any longer.
    If you have an openSUSE container, you can still use it, however you can't create any new ones.

    Testing the nixOS image currently, since officially its not supported by LXD, but seems to work well.
    Should be added soon, hopefully.

  • @Neoon said:
    Testing the nixOS image currently, since officially its not supported by LXD, but seems to work well.
    Should be added soon, hopefully.

    Nice, if you need a guinea pig for the NixOS image, give me a ping. It has a bit of a few quirks due to the closure builder sandboxing when running on containers.

  • NeoonNeoon OG
    edited April 2024

    OS / Package availability updates

    OS

    • Ubuntu can not longer be installed on 128MB due to OOM issues
    • Archlinux and Alpinelinux are now available for KVM, including the 256MB KVM Package
    • BYOOS has been removed from the 256MB KVM Package due to OOM issues
    • Rocklinux, CentOS, Almalinux and Debian are now available to be Installed on the 384MB KVM Package

    Packages

    • New 192MB LXC Package, mainly for Ubuntu but for any other distros also
    • 384MB KVM Package is also now available Norway
  • NeoonNeoon OG
    edited April 2024

    OS availability updates
    - Added Alpine 3.19 (LXC/KVM)
    - Added NixOS (LXC)

    Alpine is as before available from 64MB, NixOS from 128MB.

  • edited April 2024

    NixOS seems to be failing due to the nix-daemon's inability to remount /nix/store.

    # nix-channel --add https://nixos.org/channels/nixos-23.11 nixos
    # nix-channel --update
    error: cannot open connection to remote store 'daemon': error: writing to file: Broken pipe
    
    Apr 08 22:54:01 nixos nix-daemon[769]: accepted connection from pid 767, user root (trusted)
    Apr 08 22:54:01 nixos nix-daemon[771]: unexpected Nix daemon error: error: remounting /nix/store writable: Permission denied
    

    Don't know what LXC container backend microLXC is running (e.g., LXD, Proxmox, systemd-nspawn), but you may need to do lxc.apparmor.profile unconfined or this.

  • NeoonNeoon OG
    edited April 2024

    @jmgcaguicla said:
    NixOS seems to be failing due to the nix-daemon's inability to remount /nix/store.

    # nix-channel --add https://nixos.org/channels/nixos-23.11 nixos
    # nix-channel --update
    error: cannot open connection to remote store 'daemon': error: writing to file: Broken pipe
    
    Apr 08 22:54:01 nixos nix-daemon[769]: accepted connection from pid 767, user root (trusted)
    Apr 08 22:54:01 nixos nix-daemon[771]: unexpected Nix daemon error: error: remounting /nix/store writable: Permission denied
    

    Don't know what LXC container backend microLXC is running (e.g., LXD, Proxmox, systemd-nspawn), but you may need to do lxc.apparmor.profile unconfined or this.

    Well, yea the Image as said before is not officially supported by LXD.
    When I tested it with Incus and partially with LXD, it was working fine.

    My best guess is they added apparmor profiles for NixOS to Incus.
    Which are missing, hence he said it was not available for LXD.

    Incus LTS is available since a few days, so technically I can start upgrading the Nodes.
    However, I rather wait a bit, for other people to pentest it.

  • 26D7-D40A-F519-5E25

  • @jmgcaguicla said:
    NixOS seems to be failing due to the nix-daemon's inability to remount /nix/store.

    # nix-channel --add https://nixos.org/channels/nixos-23.11 nixos
    # nix-channel --update
    error: cannot open connection to remote store 'daemon': error: writing to file: Broken pipe
    
    Apr 08 22:54:01 nixos nix-daemon[769]: accepted connection from pid 767, user root (trusted)
    Apr 08 22:54:01 nixos nix-daemon[771]: unexpected Nix daemon error: error: remounting /nix/store writable: Permission denied
    

    Don't know what LXC container backend microLXC is running (e.g., LXD, Proxmox, systemd-nspawn), but you may need to do lxc.apparmor.profile unconfined or this.

    Well, the new LXD Images include NixOS and it seems to work fine with Nesting enabled.
    I will replace it on the Nodes so you can give it a try again.

  • NixOS has been enabled again, I replaced the current Image with a new one for LXD.
    Testing so far was fine, if nesting is enabled, don't forget that to enable it under Settings.

  • @Neoon said:

    @jmgcaguicla said:
    NixOS seems to be failing due to the nix-daemon's inability to remount /nix/store.

    # nix-channel --add https://nixos.org/channels/nixos-23.11 nixos
    # nix-channel --update
    error: cannot open connection to remote store 'daemon': error: writing to file: Broken pipe
    
    Apr 08 22:54:01 nixos nix-daemon[769]: accepted connection from pid 767, user root (trusted)
    Apr 08 22:54:01 nixos nix-daemon[771]: unexpected Nix daemon error: error: remounting /nix/store writable: Permission denied
    

    Don't know what LXC container backend microLXC is running (e.g., LXD, Proxmox, systemd-nspawn), but you may need to do lxc.apparmor.profile unconfined or this.

    Well, the new LXD Images include NixOS and it seems to work fine with Nesting enabled.
    I will replace it on the Nodes so you can give it a try again.

    Noice, thanks. I'll give it a spin.

  • edited April 2024

    @jmgcaguicla said:

    @Neoon said:

    Well, the new LXD Images include NixOS and it seems to work fine with Nesting enabled.
    I will replace it on the Nodes so you can give it a try again.

    Noice, thanks. I'll give it a spin.

    Now works great 🤌

    To NixOS friends minmaxing, a few tricks: nix-collect-garbage -d and nix-channel --remove nixos will free you some disk bringing base usage to 300M. You can then just push closures remotely (I doubt you'll be able to get the builder to run and switch on 128M anyway).

  • Had to Reboot Pakistan and Valdivia, due to the same issue that happend on JP.
    The issues just recently appeared, no clue yet, still troubleshooting why this happens.

  • NeoonNeoon OG
    edited April 2024

    OS availability updates
    - Added Ubuntu Noble Numbat (LXC/KVM)

  • edited April 2024

    Reinstalling seems to silently undo Nesting (panel still shows Disable Nesting). Just need to toggle afterwards, no biggie.

  • @jmgcaguicla said:
    Reinstalling seems to silently undo Nesting (panel still shows Disable Nesting). Just need to toggle afterwards, no biggie.

    Its recreating the container and by default it has nesting not enabled.
    Hence its disabled, however it should show it as disabled and not enabled.

    Fixed that.

  • NeoonNeoon OG
    edited April 2024

    This week I had a few cases of CPU abuse.

    So I wrote some code to add a simple CPU abuse detection system.
    This will notify users via email if the CPU usage is higher than 50% for the last 30 minutes.

    The System doesn't stop or suspend anything yet.
    However, the idea would be a strike like system.

    If you have been notified a bunch of times, your container / virtual machine will be stopped.

  • @Neoon said:
    This week I had a few cases of CPU abuse.

    So I wrote some code to add a simple CPU abuse detection system.
    This will notify users via email if the CPU usage is higher than 50% for the last 30 minutes.

    The System doesn't stop or suspend anything yet.
    However, the idea would be a strike like system.

    If you have been notified a bunch of times, your container / virtual machine will be stopped.

    Smol update.

    You will be send 3 notifications via email before the System will take action.
    Roughly 2 Hours with more than 50% CPU load.

    The 4th time you exceed the threshold your virtual machine / container will be stopped and you will be notified via email.

    I will post here again once the automatic suspension is enabled, until then, it will just send notifications.
    If you notice any bugs, feel free to let me know.

  • FritzFritz Behlnd you
    edited May 2024

    Got this email, what does this mean?

    Hey,
    
    The following containers on microLXC have been renewed:
    
    List of ips ....  will expire in 60 day(s)
    
    Any questions? You can mail us at: [email protected]
    
    microLXC
    
  • @Fritz said:
    Got this email, what does this mean?

    Hey,
    
    The following containers on microLXC have been renewed:
    
    List of ips ....  will expire in 60 day(s)
    
    Any questions? You can mail us at: [email protected]
    
    microLXC
    

    You have to login every 60 days to confirm your activity.
    This is just the confirmation email that the listed containers have been extended because you logged in.

  • Maintenance Announcement
    I have to carry out some changes on the backend, this will make the backend unavailable for roughly 1 hour or less.
    Running machines are not affected, however no tasks or deployments can be done.
    Will be done this week, Saturday, 11th of May, at around 20:00 GMT.

Sign In or Register to comment.