I created a number of jails when jailmarker came out. After Eel, I moves several of those back to docker but a couple are harder to move or I need some of the features. (ipv6 and virtual ip addresses)
I understand Fangtooth will have a different setup for jails. Will it be possible to move those to the new setup? It doesn’t need to be automatic.
Fangtooth will have Incus (LXC) support for containers.
We are not going to offer any way to migrate jailmaker to Incus LXC, however spinning up new containers and moving things over should be fairly simple.
You’d already have all the config/data/compose in datasets, shouldn’t be hard to just have those available in Incus or move to default docker if they add support for things you need.
May want to look at this thread:
Sub-question: Will existing jailmaker/systemd sandboxes keep running after upgrade to Fangtooth?
holy cow. thx for the ping stux.
hm… is incus good?
sorry i have zero info prior to this.
i’m sure other newbies like me will be thinking, how to deploy containers using incus in the new incus system? using existing docker containers.
Anyway i imagine migrating would be similar to this somewhat
but that’s using docker containers, so not sure if incus uses the same? or not 
*update
found more resources to learn more about incus
https://www.cyberciti.biz/faq/how-to-run-docker-inside-incus-containers/
How to run Docker inside Incus containers
Incus and Docker both use Linux kernel features to containerize your applications. Incus is best suited when you need system-level containers that act like traditional VMs and provide a persistent developer experience. On the other hand, Docker containers are ephemeral, i.e., temporary in nature. All files created inside Docker containers are lost when your Docker container is stopped or removed unless you stored them using volumes in different directories outside Docker. Docker is created as a disposable app deployment system. Incus containers are not typically created as disposables, and data is kept inside when they are stopped. Because of the Linux kernel support nesting feature, you can run Docker inside Incus. This page explains how to run Docker inside Incus containers.
Step 1- Creating an Incus container with a Docker and btrfs filesystem
I’ve tested this with only the BTRFS filesystem. ZFS is not supported for Docker and it is not recommended it is not recommended to use the zfs Docker storage driver for production use unless you have substantial experience with ZFS on Linux.) to use the zfs Docker storage driver for production use unless you have substantial experience with ZFS on Linux. So, it is best to stick with BTRFS as the backend driver.
wth
Running Docker in Incus Containers
ByPieter Bakker 22/11/2024
This guide demonstrates how to properly set up and run Docker inside an Incus container on Debian 12. It builds upon our previous article “Installing Incus on Debian 12 with ZFS Storage” and focuses on the secure deployment of Docker in a containerized environment.
Prerequisites
- Incus installed and configured with ZFS storage (refer to our previous article)
- Debian 12 (Bookworm) host system
- Root or sudo access
- ZFS 2.2 or later (for proper overlay support)
ok this one by pieter sounds more promising.
Anyway i hope stux or someone releases a youtube explaining this whole thing and what to do.
to keep it simple, i’m sure most newbs like myself will know about docker deployment. so they want to know if they can do the same with the incus change or not… nevermind jailmaker as that seems to be a dead end at that point. but how to deploy docker if possible under incus?
in eel using the inbuilt docker support, you can pick the image from catalog and deploy that way. OR, use the advance, then add your own docker compose yaml, and deploy that way.
I’m the type of user who deploys using a docker compose yaml, so wondering how that would work in the incus change
In the Docker in Incus is Awesome youtube video @ 2:00 he examines how to use a docker compose yaml and see if it can be deployed in Incus somehow. I guess this is really i want to know
as long as i can get dockge up and running (with the new change), and deploy all my docker container yaml from dockge, i’d be happy if that was possible in fangtooth 
this would be ideal for me also. if i can just leave my jailmaker as is, and it will continue to work in fangtooth
May also want to check out this thread in regards to incus
This thing Dan is working on seems like a possible solution. But have to see how Fangtooth works on release.
The important part mentioned for Dan’s project (jailmaker substitute using incus, in preparation for fangtooth)
FAQ
Does this work?
Yes! Standard containers work, install docker, and can install and run docker images. Mounts can write data through to your host and datasets you are assigning to your containers which are configured under
devices:andtype: diskwithshift: trueenabled.
I guess will all these big changes, i’ll just sit out fangtooth, see what the situation is then decide what to do then
Reminder: Incus/LXC is to replace officially the unofficial jailmaker system for deploying system containers. It does NOT replace docker-compose for deploying application containers.
No change to your docker containers in Fangtooth. (Unless you want to.)
thats awesome then.
i wonder what dan’s incus project will turn out like. it reminds me of how the jailmaker was deployed sort of. i’ll keep tabs on that.
but if the current docker system remains, then i’ve already tested deploying dockge using captain stux’s guide. so a list of all my docker containers are there, just not activated (since i got the jailmakers running).
All i’d have to do is simply modify the docker compose yaml in dockge for each container, so that the pathing is correct (since jailmaker uses a slighlty different pathing rather than the actual location)
so switching from jailmaker for me shouldn’t be too big a deal.
Will see how it goes 
Yes, they should.
I haven’t tested it yet, but I can’t see any reason why the incus-migrate tool wouldn’t work…
In theory you should just be able to the rootfs directory in your jail’s dataset. You would have to reconfigure the container, but it should allow importing of the container’s file system.
