DO Ideas 2

Update arch linux image

Arch has moved from sysv to systemd and newer Arch images reflect this change. Also adding 32bit image would be nice.

  • Iivari Äikäs
  • Sep 11 2018
  • Shipped
  • Attach files
  • Anonymous commented
    September 11, 2018 19:07

    Never mind. I just saw the following thread...
    https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/5812390-keep-arch-linux-on-digitalocean

    It is unfortunate. I don't think that DO needed to worry about updating their image for Arch any more regular than a non-rolling OS like CentOS, etc. Once installed, the admin can bring it up-to-date just like the others.

    Please bring Arch back!

  • Anonymous commented
    September 11, 2018 19:07

    All, was Arch available to create a droplet with a few years ago? I do not see it in the options today.

  • Moisey Uretsky commented
    September 11, 2018 19:07

    We've updated the Arch-Linux image so it should no longer break under update but we still need to roll-out kernel management support so that customers are allowed to create/update kernels as they like.

    Thanks!

  • Hargobind Khalsa commented
    September 11, 2018 19:07

    WARNING: Anyone using the Arch Linux image, make sure you DO NOT update the linux package! It contains the kernel and associated kernel modules. Since digital ocean uses a fixed kernel version this will break your machine if you reboot, no network among other problems. (The arch linux package manager pacman removes the old version so the system can no longer find kernel modules that match the currently running kernel).

    Until Digital Ocean resolves this you should probably make sure your /etc/pacman.conf includes the line "IgnorePkg = linux" to prevent it from updating the kernel and associate modules.

  • vhbit commented
    September 11, 2018 19:07

    Works now :-) Thanks a lot!

  • Moisey Uretsky commented
    September 11, 2018 19:07

    Thanks Anthony, the x64 has been updated and test for virtio and x32 will be now. =]

  • C Anthony Risinger commented
    September 11, 2018 19:07

    actually it looks like they just forgot to set to correct cmdline for the Arch image...

    my [temp] Debian image boots by LABEL:

    root=LABEL=DOROOT ro

    ...whereas the Arch one uses the device/kernel name:

    root=/dev/sda ro

    ...but the device itself is named properly:

    # blkid -p -s LABEL -o value /dev/vda
    DOROOT

    ...so once they update the cmdline, it .should "Just Work"

  • C Anthony Risinger commented
    September 11, 2018 19:07

    @vhbit, no you are not the only one :(

    the kernel cmdline (`cat /proc/cmdline`) is trying to boot /dev/sda, which of course does not exist when using virtio disks (/dev/vda).

    a simple -- non-permanent! -- fix is to symlink:

    ln -s /dev/vda /dev/sda; exit

    ...from within the mkinitcpio/busybox shell; the proper modules will be loaded accordingly... the name itself means nothing. unfortunately since this is a RAM only environment, a reboot will need the same to get going again -- open a ticket with DO.

  • Anonymous commented
    September 11, 2018 19:07

    Thank you! Now only provide Arch Linux as a distro ;)

  • vhbit commented
    September 11, 2018 19:07

    Am I the only one who gets a problem booting it if VirtIO was enabled during droplet creation?

  • Moisey Uretsky commented
    September 11, 2018 19:07

    Arch is finally back =]

  • Felipe Martín commented
    September 11, 2018 19:07

    Wonderful, needed an VPS and yesterday I started with a CentOS. At least is only for development, will replace it over the weekend waiting for an "official" response for this.

  • Hargobind Khalsa commented
    September 11, 2018 19:07

    It looks like ArchLinux images (x64 and x32) have finally appeared in the control panel! Not sure if they are waiting for something before saying something here, but I've started playing with one and it looks good so far.

  • Alexander Smith commented
    September 11, 2018 19:07

    Agreed it's not the waiting that's the issue it's the bad ETAs that make it an issue.

  • Felipe Martín commented
    September 11, 2018 19:07

    I'm actually waiting for these, and I really don't care about this taking too long for them to sort out, what really annoys me is the estimated times they give us. If you really don't know when it'll come out, just say that, I'd rather prefer to check for an ETA once a week that came for a release that didn't happen.

  • Anonymous commented
    September 11, 2018 19:07

    This is simply unacceptable. It is taking way too long and saying "next week" every time when it takes months is starting to come off as very disingenuous.

  • Alexander Smith commented
    September 11, 2018 19:07

    If they offered that reflexing they don't do a good job of letting us know. I opened a ticket a week ago (when I signed up) asking about the arch image. They said they hoped it would be available late last week. Never offered setting up a droplet for me.

  • reflexing commented
    September 11, 2018 19:07

    @C Anthony Risinger maybe if you open a ticket they will make an Arch droplet for you? I created Arch when it was available, then moved in to VirtIO and it's running exceptionally fine since.

  • C Anthony Risinger commented
    September 11, 2018 19:07

    yes, what she and Alexander Smith said.

    i actually created an account over 45 days ago, and have thus far accomplished next to nothing :( now, i've been charged next to nothing as well, so while not a blight on the service, it's an unsightly figure nonetheless...

    "expectation is the root of all disappointment"

    ...customer service is simply about managing expectations, nothing more (full-time developer, but in a past life i was top 10% sales/CSR rep). when customer holds proper expectations -- KEY: pleased with the solution OR NOT -- they be be able to make decisions best befitting of all parties.

    ...when they hold expectations founded by guess or whim, the consequences exponentiate outward and all but guarantee a net loss (share with friends/family/etc).

    the moral of the story here is that despite my 95% glowing review/evaluation of DigitalOcean, the 5% has disappointed me 45 days in a row: since i thought it was "about to be released", i check every day, with same outcome :(

    NOTE: this isn't to be taken as or directed at any given person within DO, just some general food-for-thought as to how you can improve. i am still a rather satisfied customer (albeit on Deeeebian ATM) but i prefer to be informed once, and delighted later vs. a rollercoaster... these things take time, and i need to schedule them accordingly.

  • Alexander Smith commented
    September 11, 2018 19:07

    I'm getting the feeling this will be coming with the final release of the new control panel. Mainly because that's where the new kernel management is implemented. Thus I feel we have another week or two and minimum. Which greatly saddens me since DO made it sound like it would be a lot sooner than that.

  • Anonymous commented
    September 11, 2018 19:07

    Well.... in fact i have help to the admins creating a minimal ARCH image with systemd, still waiting to the launch of ARCH to start deploying the servers, but i trust that finally this week will be available...

  • Luka Dornhecker commented
    September 11, 2018 19:07

    A real ETA would be nice. I don't feel like waiting much longer.

  • Alexander Smith commented
    September 11, 2018 19:07

    Agreed a for sure ETA would be awesome. I mean realistic of course. I would rather have it come out early than be disappointed on the day you set :P.

  • Atilla commented
    September 11, 2018 19:07

    in my current ArchLinux image WordPress installation doesn't work. My usual conf is : Nginx/PHP/Mysql/WP

    error message is: "You do not have sufficient permissions to access this page"

    I did this is installation very often so it cannot be really a problem with permissions. Something sucks...

    when will be new ArchLinux image available?

  • Felipe Martín commented
    September 11, 2018 19:07

    Do yo have a real ETA for this? You said it will be deployed last monday.

  • Moisey Uretsky commented
    September 11, 2018 19:07

    Yes, literally one of our guys is in the office right now, working on it!

    I am whipping non-stop till he gets it done =]

    One of these two sentences may or may not be true.

  • Alexander Smith commented
    September 11, 2018 19:07

    Any updates on this?

  • Moisey Uretsky commented
    September 11, 2018 19:07

    The Arch Image was removed because it was outdated and required a kernel update and we did not have a kernel management system in place yet.

    We spent this week developing the kernel management system which will pull out kernels from your running VMs and give you the ability to load those for any virtual server.

    We will be pushing this out to the front-end on Monday most likely and then we will be re-opening the old Arch image since customers will be able to run an upgrade and select whatever kernel they like.

    The next piece required us to rearchitect about how we manage supported images, to this end we are developing an ISO loader. In this case customers will be able to upload an ISO, launch it, install it, and have a VM exactly how they want it to be. We need this system in place so that we can use it to install our images that we make public for supported distributions.

    The reason that some requests get delayed as you can see is that sometimes it appears to be a very simple issue like getting a new version of Arch supported but in reality we look at every issue and ask ourselves does this require automation, does this require access on the backend, and is this something that we want to push out to the front-end for customers to use.

    So while we understand the frustration that everyone who is an Arch supporter felt while we've temporarily removed it I hope there is a bit of solace in knowing that your support for this distro has forced us to work harder on implementing some really cool features which will be launching next week, like the much waited for kernel management.

    Thanks guys & gals!

  • Luis Bacelar commented
    September 11, 2018 19:07

    Hey there...

    I recently moved from Linode to DigitalOcean after checking out your terms and seeing you had an Arch image avaliable.
    Yesterday I was preparing to migrate my servers, so I destroyed the Arch image I set up initially and was preparing to rebuild it from scratch and to my surprise this is no longer available.

    From the comments i read in your forums I would say that there are no imediate plans to make this available soon.

    To me this will be a deal breaker. I will not stay if I cannot use Arch.

    Another comment: I do understand that you would not want to support too many tickets on Arch because the previous image was a bit outdated, but still there are many reasons you should not remove the Arch image:
    1. old Arch is better than no Arch.
    2. Arch is distro for experienced users, who are used to set up their system. Less support will be well tolerated.
    3. Arch distro is a rolling distro, so this should make it a lot more "maintenance free" than the other distros you currently support. The main advantage an Arch user get is precisely not having to reinstall it's system from scratch all that often to get the latest versions of software.

    Bottom line: Please get back an Arch image (any version) on your offer.

  • Felipe Martín commented
    September 11, 2018 19:07

    Im also waiting for this. Already moved one of my companies servers from OVH, and not paying my personal VPS in OVH anymore (I had a lot of problems). I'm waiting to this to start over in DO.

  • Moisey Uretsky commented
    September 11, 2018 19:07

    Definitely not a second class citizen we are just in the middle of a couple of big projects which we will be announced soon which is slowing this down a bit unfortunately.

  • Hargobind Khalsa commented
    September 11, 2018 19:07

    Please do bring this back soon. I originally decided to investigate DigitalOcean because it appeared ArchLinux was supported only to discover that it's not currently available. While I understand the motivation and reasons for removing the image this behavior makes it seem like ArchLinux is a second class citizen which may or may not be supported at any point in the future.

  • Luka Dornhecker commented
    September 11, 2018 19:07

    Please bring Arch back ASAP.
    I tried to move my droplet to systemd but couldn't get netcfg working.

  • C Anthony Risinger commented
    September 11, 2018 19:07

    a must for me... i moved here from Linode (techically i'm still paying for both) and i intended on migrating tonight.

    all my servers and personal systems run Arch -- will need to remedy ASAP else sadly i cannot stay long :(

    i actually expected to run my own images... i see its in devel, so hopefully one or the other become available in next 30 days [max!]

    otherwise, it's been a good experience, one i hope will not be suspended/terminated before it can even start.

  • Moisey Uretsky commented
    September 11, 2018 19:07

    It was removed to reduce the number of support tickets because the one that was available was very out of date, we will be readding it as soon as we have a new image ready to go.

  • Terry commented
    September 11, 2018 19:07

    It's now removed, guys please vote up and get Arch back.

  • Matías Battocchia commented
    September 11, 2018 19:07

    For now, Arch Linux is not available for creating a new droplet.

    Support told me:

    "We currently do not have an official ETA for the Arch Linux distro. However, we do have it on the agenda to re-add it to our OS list."

  • chrisl commented
    September 11, 2018 19:07

    I have my arch droplet using systemd. The wiki article that reflexing gave works correctly.

  • reflexing commented
    September 11, 2018 19:07

    @all one doesn't need to change kernel boot line to use systemd. See https://wiki.archlinux.org/index.php/Virtual_Private_Server#Moving_your_VPS_from_initscripts_to_systemd

  • Daniel Sage commented
    September 11, 2018 19:07

    +1

    I can't setup an Arch Linux server because it can't be fully updated manually (can't change the kernel line to properly boot)

  • Oliver commented
    September 11, 2018 19:07

    +1
    waiting for systemd enabled Arch image to get started.

  • Matías Battocchia commented
    September 11, 2018 19:07

    Waiting to hop in...

  • krsanky commented
    September 11, 2018 19:07

    yes, or allow custom images

  • Matías Battocchia commented
    September 11, 2018 19:07

    +1