Incus init practice

Incus
1
  1. Installed incus.
  2. ran incus admin init

#Ran:
$ sudo incus storage show default
#
config:
size: 30GiB
source: /var/lib/incus/disks/default.img
description: “”
name: default
driver: btrfs
used_by:

  • /1.0/images/4664d6e86ba0698986a9e5ad4930937408a180db138bc2863acf6cedfcb1eb9c
  • /1.0/instances/jetty-01
  • /1.0/instances/jetty-02
  • /1.0/profiles/default
    status: Created
    locations:
  • none

#ran below to get into one of my containers
$ sudo incus exec jetty-02 – /bin/bash

#ran below to see disk in container
$df -h
#displayed
Filesystem Size Used Avail Use% Mounted on
/dev/loop8 30G 533M 29G 2% /
none 492K 4.0K 488K 1% /dev
udev 3.7G 0 3.7G 0% /dev/tty
tmpfs 100K 0 100K 0% /dev/incus
tmpfs 100K 0 100K 0% /dev/.incus-mounts
tmpfs 3.8G 0 3.8G 0% /dev/shm
tmpfs 1.5G 96K 1.5G 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock

#based on the below line listed in the results…it looks like I created a Loop disk
/dev/loop8 30G 533M 29G 2% /

I want to create containers and see all the specifics, then delete the containers, and delete the
admin init (if possible) and go thru the steps several time to see how the init options work

Is that possible?

Also, how do I assign a description to the storage
$ sudo incus storage show default
config:
size: 30GiB
source: /var/lib/incus/disks/default.img
description: “”
name: default
driver: btrfs
used_by:

  • /1.0/images/4664d6e86ba0698986a9e5ad4930937408a180db138bc2863acf6cedfcb1eb9c
  • /1.0/instances/jetty-01
  • /1.0/instances/jetty-02
  • /1.0/profiles/default
    status: Created
    locations:
  • none

Lastly
$ sudo incus storage list
±--------±-------±------------±--------±--------+
| NAME | DRIVER | DESCRIPTION | USED BY | STATE |
±--------±-------±------------±--------±--------+
| default | btrfs | | 4 | CREATED |
±--------±-------±------------±--------±--------+
#what is Used BY refer to?

There are several questions in this post. Would you prefer I post one question per post?
Regards,
Bret Stern

2

Hi!

Doing it that way (repeated installed in a sandbox), is the proper way to learn.

My suggestion is to create an Incus VM in your existing setup, then install Incus in that VM, launch containers, etc. Once you have done your experimentation, delete the VM and start over. By doing so, you would have a nice sandbox that does not affect your system in any way.

Also, see How to best ask questions on this discussion forum for formatting tips.

In your existing setup, you got Incus with 30GiB of storage (storage pool), and that storage has been placed in a file (loop file). The other option is to use a separate partition. For this learning process, it is fine as it is.

When you create a VM in Incus, your VM will get by default 10GiB of space and 1GiB of RAM. This is probably not a lot when you install Incus in there. When I do testing, that amount is fine, since I tend to use images:alpine/edge/cloud images which are tiny in terms of memory use and space. Anyway, when you launch a VM, you can specify different diskspace/memory.

See the First steps of the Incus documentation for your easy questions. For example, you do not need to use sudo all the time. Add your non-root account to the incus-admin Unix group.

You can edit fields like description by setting the appropriate key to the new value or by incus storage edit mystorage.

3

Simos,
Thank you for taking the time. Great ideas, and real encouragement.
I’m 67 and trying to get the container/VM in my everyday game.
Cheers

1 Like
4

Bret, do keep the questions coming. It helps the project to figure out any pain points and become better to new users.

1 Like