According to Oracle Cloud Free Tier \u2192 Product \u2192 Compute<\/a>, two architectures are available: <\/p>\n You also get a total of 200 GB of storage that you share for everything, from boot volumes for your VMs, to storage, backups and your custom OS images. And because each VMs uses minimum ~47 GB, that also means you can't have more than 4 free VMs total.<\/p>\n Go to cdimage.debian.org\/cdimage\/cloud<\/a> and choose a Choosing between The cloud kernel omits modules that are unlikely to be useful in a cloud environment. (\u2026) But if you're worried and don't want to mess with it, generic is a more conservative choice.<\/p>\n As for Generic vs Genericcloud, indeed, what changes is the kernel. The Put the image file to object storage<\/a><\/strong> (create a new bucket if needed). <\/p>\n Option 2, Wget\/cURL<\/strong>. Fetch the remote file right into your bucket. Click Developer Tools (top right corner) \u2192 Cloud Shell; then run:<\/p>\n If using the Archive Storage Tier, once the file appeared as object in the bucket, restore it for 24 hours \u2013 or else you'll be getting The PAR\/object provided for image import is in archived state. Please restore it and try importing again<\/em> if you try to create a Custom Image using a file that's archived. Create an OCI Custom Image<\/strong> from your bucket object. Go to Custom Images<\/a>, click Import Image<\/em> and choose Import from an Object Storage bucket<\/em>. Select the bucket where you uploaded the image, and then select the image. The image type is The new image should appear on the Custom Images<\/a> page. Wait for it to complete importing.<\/strong> Then go to Custom image details<\/em> and under Edit details<\/em> select the free tier shapes: Otherwise you won't be able to connect to your Arm VMs.<\/p>\n<\/li>\n Create an OCI VM instance<\/a>, under Placement and hardware<\/em> choose the image you have just created<\/p>\n<\/li>\n Define your SSH keys, or make sure to save the auto generated ones<\/p>\n<\/li>\n Start the instance if not started automatically<\/p>\n<\/li>\n Connect using Lastly, if you can't connect to your newly created instance - it doesn't respond to ping and SSH times out - make sure you created the necessary ingress rules and the Internet gateway exists. See this Stackoverflow answer for more info: racle Cloud Instance connectivity issue<\/a>.<\/p>\n In short:<\/p>\n Go to Virtual Cloud Networks list<\/a> and open the VCN you're using for your free VPS<\/p>\n<\/li>\n Once inside the Virtual Cloud Network Details<\/em>, go to Internet Gateways<\/em> tab. There should be at least one. Otherwise click Create Internet Gateway<\/em> and in the blade\/popup that slides from the left, just give your new gateway a name. Do not<\/strong> make any Route Table Association under Advanced options.<\/p>\n<\/li>\n Go to the Virtual Cloud Network Details<\/em> \u2192 Route Tables<\/em> tab that is neighbouring to the Internet Gateways<\/em>. Make sure you have at least one, in my case the default is named Default Route Table for my-VCN-name<\/em>. Inside, the Route Rules for that table should be:<\/p>\n Finally, under the Virtual Cloud Network Details<\/em> \u2192 Subnets<\/em> tab (located again under the same level as Internet Gateways<\/em> and Route Tables<\/em>) and open the subnet you should already have there. Then under Security Lists<\/em> open the one that's already there. Edit the Ingress Rules<\/em> (incoming traffic) and Egress Rules<\/em> (outgoing traffic).<\/p>\n Reboot the VPS after making the above changes.<\/p>\n Sources:<\/p>\n If you got a Free Tier VPS on Oracle Cloud and you want it to run Debian, you will not find it in pre-built OS images. Here’s how you create a custom OCI image based on Debian.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[778],"tags":[775,862,817],"class_list":["post-1059","post","type-post","status-publish","format-standard","hentry","category-cloud-serverless","tag-debian","tag-oracle-cloud-infrastructure","tag-vps","entry"],"_links":{"self":[{"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/posts\/1059","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/comments?post=1059"}],"version-history":[{"count":12,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/posts\/1059\/revisions"}],"predecessor-version":[{"id":1829,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/posts\/1059\/revisions\/1829"}],"wp:attachment":[{"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/media?parent=1059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/categories?post=1059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/editjournal.redakt.eu\/faxmodem\/wp-json\/wp\/v2\/tags?post=1059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nImportant<\/strong>: to be able to connect to these Arm instances, you will have to make some simple changes to your OS image - see below.<\/li>\n<\/ul>\nDebian Images<\/h2>\n
\n
qcow2<\/code><\/strong> image for your architecture<\/strong>: arm64<\/code> for Arm<\/strong> and amd64<\/code> for AMD<\/strong>.<\/p>\n\n
generic<\/code> and genericcloud<\/code>:<\/p>\n\n
\nidea behind the Generic image is that the image can be used with Ironic,
\non baremetal hardware, where the Genericcloud may not.<\/p>\n<\/blockquote>\n<\/li>\n\n
wget https:\/\/example.com\/file.iso\noci os object put -bn my-bucket --file file.iso<\/code><\/pre>\n<\/li>\n<\/ul>\n
\nMy advice is to restore for 24 hours because restoring takes long, and if you choose 24 hours, you have room to return to this the next day while the file is still there.<\/p>\n<\/li>\nQCOW2<\/code> and I kept Paravirtualized mode<\/em>.<\/p>\n<\/li>\nVM.Standard.E2.1.Micro<\/code> for AMD and VM.Standard.A1.Flex<\/code> for Arm; you can deselect other shapes.
\n4.1. Arm-specific note<\/strong>: on the same Custom image details<\/em> page click Edit image capabilities<\/em> and set the following:<\/p>\n\n
UEFI_64<\/code> checked and selected as preferred; BIOS<\/code> deselected<\/li>\nCUSTOM<\/code> checked and selected as preferred; everything else deselected<\/li>\nDisabled<\/code><\/li>\n<\/ul>\nssh -i \/path\/to\/private\/key -p 22 debian@ip<\/code>
\nIf you changed the SSH port during install, see amending OCI firewall rules<\/a>.
\nImportant<\/strong>: debian<\/code> is the username to log in with, and as always, you can elevate to root using sudo su -<\/code>.<\/p>\n<\/li>\n<\/ol>\n\n
\n
0.0.0.0\/0<\/code><\/li>\nInternet Gateway<\/code><\/li>\nStatic<\/code><\/li>\n<\/ul>\n<\/li>\n\n
No<\/code>, Source<\/em> = 0.0.0.0\/0<\/code>, IP Protocol<\/em> = TCP<\/code>, Source Port Range<\/em> = All<\/code> and Port<\/em> = (whatever port you need to allow access to, e.g. 22<\/code> for SSH or 80,443<\/code> for HTTP)<\/li>\nAll Protocols<\/code> and no ports defined at all, thus allowing all outgoing traffic<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n