As reported first by @edorgeville in [the discuss.linuxcontainers.org thread](https://discuss.linuxcontainers.org/t/early-development-version-of-the-resurrected-incus-compose-online/25690/30), the current incus-compose behaviour differs from the incus CLI in that it defaults to using the `local` remote, even when a different one is selected via `incus remote switch <remote name>`. Even though the `--remote` CLI flag and `$INCUS_REMOTE` env var are offered, it would be great if incus-compose could reuse the currently active remote by default to stay in line with the upstream incus behavior. Thanks!