Linux Jails (sandboxes / containers) with Jailmaker

my experience with jailmaker

whenever u get that error message, most often the reason is the jailmaker docker jail’s config has something wrong in it.

solution?

undo the last change you did there recently that might be the cause.

OR, if you can’t remember, go back to the default docker config template, try use that. If it works, starting more changes to it, BIT by BIT, until you come across the cannot run warning. Then roll back your change that made it go bad. That’s your culprit.

hope that helps with the troubleshoot

Made this for myself but maybe it will help you, and pretty much the summary of what i just said


:rofl:

why jail docker-compose?

i did jail docker.

my layout in my docker dataset looks like this

/mnt/tank/docker

then within that is

/compose
This is where i have my docker yaml for deploying dockge the first time

/stacks
this is where all my docker yamls and .env go when i deploy through dockge. each container has their own folder inside

/data
this is where all the docker container permanent configs go. each container has their own folder inside

/old-archived
this is from my old nas where i restored from. i use this for reference when deploying my dockers using old stuff. will eventually delete

then you got /mnt/tank2/videos , /mnt/tank2/pictures for media. you also need to bind this dataset in the docker jail config in addition to the docker dataset

anyway why i suggest to name your jail, docker instead of docker-compose, is so whenever you do jlmkr command its jlmkr status docker instead of jlmkr status docker-compose less to type and to the point. no need the extra :sweat_smile: then again if you are copy pasting that, it wouldn’t matter either way i guess

hope that helps

1 Like