Report this

What is the reason for this report?

Problem with Fedora Custom Images

Posted on June 17, 2019

Created a Fedora 28 image using Packer/Virtualbox for upload as a custom image. Upload completes sucessfully, but when starting a droplet the instance hangs with console message “A start job is running for dev-disk …” and never gets beyond that. I’ve tried wit/without swap, removing the UUID designations from /etc/fstab, and copying EXACTLY all of the relevant cloud.cfg and other configs from a Fedora droplet provided by Digital Ocean. We also build Ubuntu 18.04 images and these work without a problem.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello,

Any Linux OS that supports ext3/4 file systems and has cloudinit 0.7.7, cloudbase-init, coreos-cloudinit, ignition, or bsd-cloudinit installed should work with the import tool.

Currently, ISO files are planned to be supported towards the end of 2018. If you would like to upload an ISO file, we suggest first booting the ISO into your VirtualBox (or your favorite virtualization tool) to generate a supported file type, and then importing that file into our Custom Image tool.

https://www.digitalocean.com/blog/custom-images

Regards

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.