microLXC Public Test

145791015

Comments

  • @Neoon said:

    @ralf said:

    @Neoon said:
    Reminder, SG (Nexusbytes) has been set out of stock since months, however we still got a bunch of containers running.
    This Location could go offline this week, according to sources.

    Ooooh, I have one. Do I need to do anything, or just wait and see what happens to it? I can happily terminate my container if that'd be useful as I only use it occasionally for checking connectivity to elsewhere.

    You can watch it burn if you want.

    Remember when OVH was on fire and there was a screenshot of one if the servers thermals monitoring. Ill be like that

    Synteq Technical Support, Technical Writer.
    Contact me at: +1 (307) 428 8111 or [email protected]

  • Thank you 🇯🇵

  • FritzFritz Behlnd you

    Hi @Neoon Auckland lxc is having problem I guess.
    I can't ssh into it. Connection refuse.

    I'll try to terminate and re launch.

  • @Fritz said:
    Hi @Neoon Auckland lxc is having problem I guess.
    I can't ssh into it. Connection refuse.

    I'll try to terminate and re launch.

    The Machine has been rebooted from the ISP, there was no maintenance announcement or anything.
    Besides that, I don't see anything wrong.

  • The Monitoring didn't picked up the reboot, iptables forwarding rules where not applied.
    Should be fixed.

  • FritzFritz Behlnd you

    @Neoon said:
    The Monitoring didn't picked up the reboot, iptables forwarding rules where not applied.
    Should be fixed.

    Everything is working now! ;)

  • 8e93-6011-cf98-0168
    Thank you.

    MicroLXC is lovable.

  • I dislike the current state of microlxc.
    The ongoing issues with LXD, ongoing Network issues in some Locations, does not really reach the quality level I wanted to provide.

    Plus, I can only code for a few hours per day and I have a lot of projects to code on.
    Hence I made the decision to close the registration for new accounts, for now.

    No, I don't have in mind to kill the project, however, purging LXD and replacing it internally with Proxmox, which is more reliable in the long run.
    Yea I know Bookworm is going to ship with LXD, without snap, however I don't know if this would make LXD feasible again.

    That would be a thing to figure out.

  • Likely in 4-6 weeks I am going to have 1-2 nodes available to carry out a test for Debian 12 / Bookworm with LXD.
    This Test will be Public as before, however time limited.

    Approximately 3 months, up to 6 months, if it's a success indefinitely.
    At this point I would either switch the rest of the systems to Debian 12 or Proxmox.

  • Mentally strong people use plain LXC.

    lxc-create
    lxc-unpriv-start
    lxc-unpriv-attach
    

    LXC has fewer layers.
    It allows more precise control and customization.

    We accept Karma donations for the last flan. 🍮 affbrr

  • @Neoon said:
    I dislike the current state of microlxc.
    The ongoing issues with LXD, ongoing Network issues in some Locations, does not really reach the quality level I wanted to provide.

    Plus, I can only code for a few hours per day and I have a lot of projects to code on.
    Hence I made the decision to close the registration for new accounts, for now.

    No, I don't have in mind to kill the project, however, purging LXD and replacing it internally with Proxmox, which is more reliable in the long run.
    Yea I know Bookworm is going to ship with LXD, without snap, however I don't know if this would make LXD feasible again.

    That would be a thing to figure out.

    Is the code still open? Nothing related appears on GitHub anymore.

  • @adly said:

    @Neoon said:
    I dislike the current state of microlxc.
    The ongoing issues with LXD, ongoing Network issues in some Locations, does not really reach the quality level I wanted to provide.

    Plus, I can only code for a few hours per day and I have a lot of projects to code on.
    Hence I made the decision to close the registration for new accounts, for now.

    No, I don't have in mind to kill the project, however, purging LXD and replacing it internally with Proxmox, which is more reliable in the long run.
    Yea I know Bookworm is going to ship with LXD, without snap, however I don't know if this would make LXD feasible again.

    That would be a thing to figure out.

    Is the code still open? Nothing related appears on GitHub anymore.

    It was never open source.

    @yoursunny said:
    Mentally strong people use plain LXC.

    lxc-create
    lxc-unpriv-start
    lxc-unpriv-attach
    

    LXC has fewer layers.
    It allows more precise control and customization.

    I don't think LXD itself is to blame, I rather think, that additional shit what is shipped with snap packages, are causing issues.
    The shit I have seen with Ubuntu 20.04 and snap, applications before never having issues and out of the sudden, are slower and randomly crashing or getting unresponsive.

    Chromium on Ubuntu, its a crap experience.
    You are loosing like 20%-30% alone on performance.

  • @Neoon said:

    @adly said:

    @Neoon said:
    I dislike the current state of microlxc.
    The ongoing issues with LXD, ongoing Network issues in some Locations, does not really reach the quality level I wanted to provide.

    Plus, I can only code for a few hours per day and I have a lot of projects to code on.
    Hence I made the decision to close the registration for new accounts, for now.

    No, I don't have in mind to kill the project, however, purging LXD and replacing it internally with Proxmox, which is more reliable in the long run.
    Yea I know Bookworm is going to ship with LXD, without snap, however I don't know if this would make LXD feasible again.

    That would be a thing to figure out.

    Is the code still open? Nothing related appears on GitHub anymore.

    It was never open source.

    Perhaps it is NanoKVM I was thinking of? I remember a NanoKVM-Tools repo.

  • @adly said:

    @Neoon said:

    @adly said:

    @Neoon said:
    I dislike the current state of microlxc.
    The ongoing issues with LXD, ongoing Network issues in some Locations, does not really reach the quality level I wanted to provide.

    Plus, I can only code for a few hours per day and I have a lot of projects to code on.
    Hence I made the decision to close the registration for new accounts, for now.

    No, I don't have in mind to kill the project, however, purging LXD and replacing it internally with Proxmox, which is more reliable in the long run.
    Yea I know Bookworm is going to ship with LXD, without snap, however I don't know if this would make LXD feasible again.

    That would be a thing to figure out.

    Is the code still open? Nothing related appears on GitHub anymore.

    It was never open source.

    Perhaps it is NanoKVM I was thinking of? I remember a NanoKVM-Tools repo.

    Yea, I removed the NanoKVM-Tools repo, since it was outdated and kinda janky.
    if there is interest, I might upload the better code and network setup.

  • IPv6 died in NL, working on it.

  • @Neoon said:
    IPv6 died in NL, working on it.

    Fixed.

  • somiksomik OG Hostbusters

    @Neoon I saw on your signup page you are asking for "public key" instead of "password" for the VPS setup. This is very good thing to do and I hope more and more providers starts doing this. Using a password for a server, specially if you enable root ssh access, is VERY insecure.

    I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.

  • edited April 2023

    I decided to spin up a microlxc instance in Auckland last night to run a few mtrs to my other servers, but it looks like something went slightly wrong with IPv6 setup. It's the debian template if that's relevant.

    In the control panel the address is ... ::2, but the container actually has a randomised address in the same /64.

    There doesn't seem to be an /etc/network/interfaces, so not sure this gets set up in lxc. Is this configured host-side or can I just make the interfaces file like I would on a KVM instance?

  • @ralf said:
    There doesn't seem to be an /etc/network/interfaces, so not sure this gets set up in lxc. Is this configured host-side or can I just make the interfaces file like I would on a KVM instance?

    make the interface file

    "How miserable life is in the abuses of power..."
    F. Battiato ---

  • @ralf said:
    I decided to spin up a microlxc instance in Auckland last night to run a few mtrs to my other servers, but it looks like something went slightly wrong with IPv6 setup. It's the debian template if that's relevant.

    In the control panel the address is ... ::2, but the container actually has a randomised address in the same /64.

    There doesn't seem to be an /etc/network/interfaces, so not sure this gets set up in lxc. Is this configured host-side or can I just make the interfaces file like I would on a KVM instance?

    If your VM or Container gets a /64 IPv6, the initial IPv6 is randomly (by mac) assigned by dnsmasq.
    It doesn't update in the Panel, yet.

  • @ralf said:
    I decided to spin up a microlxc instance in Auckland last night to run a few mtrs to my other servers, but it looks like something went slightly wrong with IPv6 setup. It's the debian template if that's relevant.

    In the control panel the address is ... ::2, but the container actually has a randomised address in the same /64.

    There doesn't seem to be an /etc/network/interfaces, so not sure this gets set up in lxc. Is this configured host-side or can I just make the interfaces file like I would on a KVM instance?

    I pushed a patch, the current IPv6 should be now reflected in the Panel.
    However, only for new Deployments or if you Reinstall your VM, since the database still has the old ::2 as record.

  • @Abdullah dropped a fat SG Machine, which gives me the opportunity to use a different storage backend.
    Hence I likely open the registration again, since the other stuff is delayed, so this can be tested meanwhile.

  • Neoon said:
    @Abdullah dropped a fat SG Machine, which gives me the opportunity to use a different storage backend.
    Hence I likely open the registration again, since the other stuff is delayed, so this can be tested meanwhile.

    image

  • @Ganonk said:

    Neoon said:
    @Abdullah dropped a fat SG Machine, which gives me the opportunity to use a different storage backend.
    Hence I likely open the registration again, since the other stuff is delayed, so this can be tested meanwhile.

    image

    SG is not ready jet, IPv6 is not working as expected, will hopefully get it fixed this week.

  • New ETA for SG is Friday.

  • NL was down, its partially back up, prob. router issue.
    As of right now, someone is looking into it.

  • @Neoon said:
    New ETA for SG is Friday.

    No update yet, still waiting for the Subnet to get routed.

  • @Ganonk said:
    image

    IPv6 still won't work without a nppd proxy and I won't use that.
    No ETA.

  • @Neoon said:

    @Ganonk said:
    image

    IPv6 still won't work without a nppd proxy and I won't use that.
    No ETA.

    Was Japan restocked or I saw it as available because someone deleted their server ?

    Why?

  • @jmaxwell said:

    @Neoon said:

    @Ganonk said:
    image

    IPv6 still won't work without a nppd proxy and I won't use that.
    No ETA.

    Was Japan restocked or I saw it as available because someone deleted their server ?

    There was no restock.

  • NeoonNeoon OG
    edited May 2023

    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.
    Thanks to @Abdullah / https://webhorizon.net/

    Currently 2 Packages are available.

    • 1x Core (25%), 256MB, 3GB ZFS, 200GB with 50Mbit (default package)
    • 1x Core (50%), 512MB, 5GB ZFS, 200GB with 150Mbit

    If you have any suggestions, lemme know.

  • @Neoon said:
    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.

    Currently 2 Packages are available.

    • 1x Core (25%), 256MB, 3GB ZFS, 200GB with 50Mbit (default package)
    • 1x Core (50%), 512MB, 5GB ZFS, 200GB with 150Mbit

    If you have any suggestions, lemme know.

    Thank you Neoon for providing free LXC's

    how can we pay you back?

  • @ehab said:

    @Neoon said:
    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.

    Currently 2 Packages are available.

    • 1x Core (25%), 256MB, 3GB ZFS, 200GB with 50Mbit (default package)
    • 1x Core (50%), 512MB, 5GB ZFS, 200GB with 150Mbit

    If you have any suggestions, lemme know.

    Thank you Neoon for providing free LXC's

    how can we pay you back?

    You can thank @Abdullah for providing the resources.

  • @Neoon said:

    @ehab said:

    @Neoon said:
    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.

    Currently 2 Packages are available.

    • 1x Core (25%), 256MB, 3GB ZFS, 200GB with 50Mbit (default package)
    • 1x Core (50%), 512MB, 5GB ZFS, 200GB with 150Mbit

    If you have any suggestions, lemme know.

    Thank you Neoon for providing free LXC's

    how can we pay you back?

    You can thank @Abdullah for providing the resources.

    we'll when ever you want coffee or visiting Finland please let me know.
    as for @Abdullah he can post a Flash sale here and we might get it :)

  • @ehab said:

    @Neoon said:

    @ehab said:

    @Neoon said:
    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.

    Currently 2 Packages are available.

    • 1x Core (25%), 256MB, 3GB ZFS, 200GB with 50Mbit (default package)
    • 1x Core (50%), 512MB, 5GB ZFS, 200GB with 150Mbit

    If you have any suggestions, lemme know.

    Thank you Neoon for providing free LXC's

    how can we pay you back?

    You can thank @Abdullah for providing the resources.

    we'll when ever you want coffee or visiting Finland please let me know.

    Sure I will.

  • BIG THANKS TO @Neoon & @Abdullah & ALSO OTHER SPONSORS !!
    LOVE YOU GUYS !! <3 <3 <3

    and ofcourse i give back support by having two services from Webhorizon

  • Neoon said:
    SG is available now, including a /64 IPv6 routed subnet, dnsproxy and haproxy support.
    Thanks to @Abdullah / https://webhorizon.net/

    image

  • is available for PTR/rDNS on ipv6 ?

  • @Ganonk said:
    is available for PTR/rDNS on ipv6 ?

    I didn't ask him to delegate the namervers for the subnet yet, so it ain't working.

  • many stock on any locations :3

  • @Ganonk said:
    many stock on any locations :3

    Yes because a bunch of people migrated to SG after it was added.
    Also, Bookworm just has been added.

  • @Neoon said:
    Also, Bookworm just has been added.

    Ooh, will be reflashing!

  • @mwt said:

    @Neoon said:
    Also, Bookworm just has been added.

    Ooh, will be reflashing!

    Maybe you can do a normal apt-get update, not tested on LXC though.

  • @Neoon said:

    @mwt said:

    @Neoon said:
    Also, Bookworm just has been added.

    Ooh, will be reflashing!

    Maybe you can do a normal apt-get update, not tested on LXC though.

    Yeah it's possible to do in-place upgrade no need to reinstall. I have done it before on Proxmox LXC templates.

  • NL is currently down, waiting for switch replacement, to bring it back up.

  • Patch deployed, took a bit longer because I had to reinstall my dev enviroment.

    • Registrations are open, again
    • a few small UI changes including removing the progressbar for existing users
    • Network class partially rewritten, to simplify /64 prefix allocation and IPv4 network allocation
    • Allocated IPv6 address is displayed in the Panel
    • Traffic counting updated for LXD 5.x / simplified
Sign In or Register to comment.