Disregard3145

🕷🕸

For simplicity its easiest to imagine it as a simulator or emulator. Its not trying to be your machine (called the host machine) pretend it doesn't actually use your os, or software.

Imagine each container is a fresh new machine on your desk with a blank hard drive. The image is basically the result of a set of instructions (a Dockerfile) that docker follows to install all the stuff you need to get the machine running.

Normally it starts by installing an os like alpine Linux (alpine publish this docker image and you simply build on top of that)

Then you install any extra utilities and software you might need to run the programming, maybe python or Java (again there are images themselves based on alpine managed and updated by official sources)

Finally you install what you want and tell the computer that's what to run when it boots up (often the software you want to run gives an official docker image which has done all this for you)

So when you run a docker image its actually done all this setup for you already and just stored the resultsin a way that it can apply it straight to your shiny new container in an instant and be ready.

Docker compose is instructions on how to set up a bunch of computers with a network.

Self hosting what?

In general

1. Install docker
2. Copy and paste docker run commands from the getting started guide
3. Learn from mistakes

What on earth was the word?

Unfortunately crashes jerboa

The simple answer is its hard and slow so you make a compromise.

More often than not you can find a appropriate upper bound for resolution on your target platform and rasterise ahead of time into texture atlases and the like.

You could also do this at runtime to support arbitrary resolutions but memory becomes a concern at a point. And including a rasteriser for your vector graphic format of choice may not be appropriate.

Basically using bitmaps and hoping nobody looks real close is a compromise you hope nobody notices.