# Incus 6.3 Runs Docker!

**URL:** https://discussion.scottibyte.com/t/incus-6-3-runs-docker/451
**Category:** Uncategorized
**Created:** [July 12, 2024, 8:02am UTC](https://discussion.scottibyte.com/t/incus-6-3-runs-docker/451 "2024-07-12T08:02:41Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![scott](https://discussion.scottibyte.com/letter_avatar_proxy/v4/letter/s/3e96dc/32.png) [@scott](https://discussion.scottibyte.com/u/scott)
#### Post date: [July 12, 2024, 8:02am UTC](https://discussion.scottibyte.com/t/incus-6-3-runs-docker/451/1 "2024-07-12T08:02:41Z")

</div>

This is about the new Incus 6.3 release. Introduced in this version is new OCI image support capability that allows the creation of an Incus container to run a docker application from a direct image download from the docker hub.

Beginning in Incus 6.3 it is possible to use Docker/Open Container Initiative (OCI) images directly through Incus. If you follow my channel you know that I frequently show how to nest docker applications in Incus containers.

To upgrade to the latest version of incus on your existing incus server.

```auto
sudo apt update && sudo apt upgrade -y

```

Check your version of incus:

```auto
incus --version

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/9/9ff23d955bf649bcb860c04f5533296c7fafc8dd.png)

If the above did not perform the upgrade to 6.3 then do this:

```auto
sudo apt dist-upgrade

```

Incus has containers, Incus Virtual Machines and now Incus Docker/OCI images. This is a new capability and not fully implemented. For now, it is easy to create Incus Docker images for simple docker applications.

Normally, Incus pulls its images from [linuxcontainers.org](http://linuxcontainers.org). You can also add your own servers to the list of servers that you manage remotely. To list your Incus remote server sources:

```auto
incus remote list

```

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/1/1faae0a539dc8e9ebe5d3ef2c62e1b39665a2fe1.jpeg)

To add the repository for the docker hub:

```auto
incus remote add docker https://docker.io --protocol=oci 

```

You should now see the docker repository listed.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/c/ca68cdeefcaab07d3fc700feb69fa922903141f5.png)

As a simple example of creating a Docker application container in Incus (Note: the bridgeprofile is covered in my [Incus Containers Step by Step](https://www.youtube.com/watch?v=ULPuU9aKyoU) tutorial).

```auto
incus launch docker:jgraph/drawio Draw -p default -p bridgeprofile

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/9/9dc6f3792e9d35c0cc981b64ad6731e9d0482e73.png)

Next, I do a listing to see the LAN address where my container is running.

```auto
incus list

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/5/5abddd92382fded9d0c20765e2ddcb63c4446c60.jpeg)

I go into my web browser and visit 172.16.1.62 at port 8080 because that is the documented port for the [draw.io](http://draw.io) container.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/c/cc48efc160c35267a9377a776ab746c3a75b7a25.jpeg)

It is also notable that you can pass parameters to your docker application with command switches:

```auto
incus launch docker:jgraph/drawio Draw -p default -p bridgeprofile -c environment.TZ=America/Chicago

```

I am excited about where this new Docker OCI capability is going in Incus.