Names for jails
The jails of a project find each other by name. db.shop.internal, or just db, and the names follow what runs: nothing to write, nothing to keep in step.
The idea
A name instead of an address.
The jails of a project reach each other by name. A jail called db in the project shop is db.shop.internal: the jail, the project, and internal.
Nothing to write down and nothing to keep in step. When the address of a jail changes, its name still leads to it.
The short name
Inside the project, the project is understood.
A jail says just db. Its resolver adds the project for you, so the short name and the long one reach the same jail:
$ jailops exec web -- ping -c 1 db $ jailops exec web -- ping -c 1 db.shop.internal
Use the short name in what the jail runs, and the long one when you talk about a jail from outside its project.
The host
One name for the machine.
The host as the jails of a project see it is host.shop.internal, or just host. It is the address of the host on their network: where the resolver, a package mirror or a log collector on the host is.
IPv4, IPv6 or both
Three names for each jail.
A name without a label has both kinds of address. Put v4 or v6 in front of the project to ask for one:
db.shop.internal: IPv4 and IPv6, whatever the jail has.db.v4.shop.internal: the IPv4 address only.db.v6.shop.internal: the IPv6 address only.
A jail that has only IPv6 has the first and the last. The host answers to host and host.v4.
The names follow what runs
Create it, and it is there.
A jail that runs has a name. Start one, create one, rename one, stop or delete one, and the names change by themselves, within moments:
$ jailops create cache --image freebsd-15-1 --network lan --storage default --start $ jailops exec web -- ping -c 1 cache
A stopped jail has no name, and a deleted one has none for good. Nothing is left to clean up.
Only your own project
Projects keep their names to themselves.
A jail sees the names of its own project and of no other. A jail in shop that asks for postgres.blog.internal gets no answer, and the other way round. Everything else a resolver knows, example.org and the rest of the internet, works as always.
It follows the idea that a project is a boundary. Between projects you use addresses, and a firewall rule says who may reach whom.
Nothing to set up
If the host runs local-unbound.
The names are answered by the resolver of the host, the base system's local-unbound. jailops-setup offers to turn it on when you set the host up, and from then on there is nothing to configure: JailOps hands the resolver the names, and the jails ask the host.
To see where you stand:
$ jailops doctor | grep dnsIt says not used until the host resolver is on, and what is missing, with the one command that fixes it, when something is.
Whether the resolver of the host asks other resolvers or finds the answers from the root servers itself is the business of that resolver, and its own documentation says how to change it.
An example
A web jail and its database.
The database jail is called db. The web jail asks for it by name, in a command and in its configuration:
$ jailops exec web -- psql -h db -U web shop
# in the configuration of the web application
DATABASE_URL=postgres://web@db:5432/shopIf the database jail is rebuilt and gets another address, nothing in the web jail changes. Add a rule that lets the web jail in (jailops app allow db --from jail:web) and the name does the rest.
Why .internal
A name that stays yours.
.internal is set aside for private use and never becomes a name on the internet, so it can never lead somewhere else. .local would not work: that is multicast DNS, and a resolver sends it out on the network instead of asking the host.
See also
- Who may reach what: A firewall you can read.
- Projects as boundaries: Projects are boundaries.
- How the network is built: Networks the host controls.
More articles
Jail updates without cron
Replace the nightly script that upgrades every jail: automatic jail upgrades per image, with a health check, a rollback and a record of every run, what they leave alone, and how a new FreeBSD release comes in.
Read the article: Jail updates without cronJail search and shell
Ctrl+K, a few letters, Shift+Enter: find a jail by name, label or app and open its shell. Labels that filter the jail list, bash in new jails, and the jailops command next to every step.
Read the article: Jail search and shellGetting started with the JailOps CLI
Root on the host, the command line and nothing else: install JailOps, build an image, create a network and a jail, reach it by name, snapshot it, open a port and install an app.
Read the article: Getting started with the JailOps CLIJailOps on a netcup server, with IPv6 that stays up
A /64, a router pair and a FreeBSD default that drops their probes. How every jail gets its own IPv6 address on netcup, and the one sysctl that ends the random unreachable alerts.
Read the article: JailOps on a netcup server, with IPv6 that stays upOne small cloud server, many services, solid IPv6
Run your database, web tier and workers on one low-cost server, each jail with its own IPv6 address, and fix the alerts a shared /64 causes with one sysctl.
Read the article: One small cloud server, many services, solid IPv6Write your own app: memcached, from package to catalog
Turn a small FreeBSD package into a JailOps app: the definition line by line, the offline check, a local install, the five traps, and the pull request that puts it in the catalog.
Read the article: Write your own app: memcached, from package to catalogFrom catalog to running service in one command
Install nginx from the app catalog with one command, see each of its steps, and find the data, the configuration, the logs and the snapshot afterwards.
Read the article: From catalog to running service in one commandA firewall you can read
Policies, address sets and jails by name (jail:web), each with a comment, so the firewall can be reviewed by someone who did not write it.
Read the article: A firewall you can readPostgreSQL and git, closed except for who needs them
Close a database and a git server, then let in exactly the web jail and the office, with a comment on every entry.
Read the article: PostgreSQL and git, closed except for who needs themProjects are boundaries
A project is a boundary. Another project is an external host, so only addresses cross it, written out on both sides. Why that is simpler to review, and what a project does not isolate.
Read the article: Projects are boundariesThe life of a jail
A jail starts at boot only when you declared it with --autostart. Why JailOps does it this way, how the order is decided, and how to see it with jailops boot.
Read the article: The life of a jailTab completion for jailops
Press Tab and get the names of your jails, networks and firewall policies, even on another host. How to install and turn on completion in bash, zsh and fish.
Read the article: Tab completion for jailopsTest the firewall before you trust it
Ask the firewall whether a connection would pass, and why, before you try it. Read the answer, put it in a script, and know what it cannot tell you.
Read the article: Test the firewall before you trust itSee a connection before it happens
Pick a From and a To, a protocol and a port, press Run, and see the connection flow through the firewall: what passes, what stops it, and which rule decides.
Read the article: See a connection before it happensLimit what a jail can use
Give a jail a ceiling for memory, processes, CPU, disk, firewall states and bandwidth, one command each, and know what happens when it reaches it.
Read the article: Limit what a jail can useStop every jail cleanly when the host shuts down
A host that reboots should stop its databases before it stops the disks. How JailOps stops the jails in order, and how to start them in order again.
Read the article: Stop every jail cleanly when the host shuts downOne line in pf.conf
The host's firewall stays yours. JailOps asks for one line, and everything for the jails lives below it.
Read the article: One line in pf.confWhat the host tells you by itself
A pool that reports an error, an uplink that goes down, a jail that reaches a limit: they show up in the event stream by themselves.
Read the article: What the host tells you by itselfNetworks the host controls
No bridge, no DHCP. The host hands out the addresses, gives each jail a link of its own and is the router, so jails cannot see or impersonate each other.
Read the article: Networks the host controlsVolumes: data that outlives a jail
Keep the data in a volume and the jail disposable. One volume can be attached to several jails, has its own snapshots and its own backup.
Read the article: Volumes: data that outlives a jailBack up volumes once
One copy of a volume, however many jails use it. Leave volumes out when you want to, bring them back with the jail.
Read the article: Back up volumes onceA private Docker registry
A registry of your own with users in a file: one jail, docker-registry and docker-auth, htpasswd for the passwords, the images on a volume.
Read the article: A private Docker registry
Try it on one server.
Try the console from the screenshots, install on a clean FreeBSD 15.1 machine, or add JailOps to a host you already run.