Incus-compose 1.0 has been released

News
,
21

No, just for building if you build containers from Dockerfiles.

1 Like
22

I had to install skopeo , in order to pull from registries.

23

Hey @blurry,

with 1.0.0 ? Thats a bug. But I can’t reproduce it, I installed ic in a fresh Arch Linux and tried it.

Do you mean server side? That was/is expected, maybe we should make skopeo a dependency of incus.

[r3j0@dev02 ~]$ incus-compose -P simple-nginx up
ensure   image              docker.io/nginx:alpine                 [done]
ensure   network            default                                [done]
ensure   instance           web-1                                  [done]
start    instance           web-1                                  [done]
[r3j0@dev02 ~]$ skopeo
-bash: skopeo: command not found
[r3j0@dev02 ~]$ incus-compose version
incus-compose version 1.0.0
24

Sorry, yes - on the Ubuntu 26.04 server/host side. Incus was installed via the Zabbly repo. It took me a while to figure why I was getting failures to parse the image url.

25

I see why, you didn’t see skopeo errors?

I’ll update the docs to make sure others wont have this issue, thank you!

26

Also, the skopeo version 1.4.1 packaged with Ubuntu 22.04 did not like non-Docker hub image references. I had to download a current binary GitHub - podman-container-tools/skopeo: Work with remote images registries - retrieving information, images, signing content · GitHub

27

Thank you blurry :slight_smile: I update docs - getting-started@oci-image-remotes

28

@stgraber can we ship skopeo with Zabbly repos and make it a dependency of incus ?

EDIT: shipping a foreign package is maybe to much.

29

skopeo is in the Zabbly package, it’s at /opt/incus/bin/skopeo

30

Well that was a silly mistake on my part. I needed to add /opt/incus/bin to my path.

:face_with_open_eyes_and_hand_over_mouth:

31

I don’t think so you have to, incusd should have it in its path.

I’ll setup 22.04 soon and test this.

32

I must have been doing things in a non-standard way. On a couple of 22.04 and 26.04 systems, I had the parsing failures until I installed skopeo. Sorry to cry wolf.

33

No, I have the same issue. I installed skopeo on all my systems cause of that, but forgot to document it.

I have to test more to make sure this is not an incus-compose bug.

34

It’ll be July 13 @ 2pm CDT / 7pm UTC (normalized to your timezone: 2026-07-13T19:00:00Z). Sorry for any confusion!

1 Like
35

skopeo was needed for incus-compose until 1.0.0-rc.2 - the last version before the 1.0 release.

I think that was the problem @blurry which did a lot beta tests had.

36

I love this timezone thing you did with the forums, even looked at the source code.

2026-07-23T08:13:00Z ← hihi

37

All my stacks are now in the docs.

38

hi I’m trying out the cli and it’s great!

I was wondering if there would be a way to make read only bind mounts or as a alternative watch/sync work on a remote server.

see Use Compose Watch | Docker Docs this allows local like workflow with config files pushed to the container on demand

A container could be created stopped then the file/folder copied with incus file push and then the container started.

1 Like
39

Hey @tort ,

bind only seeding should already work, there is no watch yet, didnt know it exists :slight_smile:

I forgot to document that.

40

Thanks for your time that was the missing link for my IncusOS based cluster. On my way to update my stacks I might contribute some to the docs later :slight_smile:

1 Like