That’s a very good point and can’t believe I didn’t think of that! Surely the British army would have to protect “his majesty’s realm” or some bollocks like that.
I just read that Canada hosts Britain’s largest overseas base, although it seems to be for training purposes.
From the UK and personally, 100% yes but not sure I feel the rest of the population would agree. I mean, a lot of us turned our backs on the EU and there’s a lot of cross over with US right wing nutters.
However, I would believe that when push comes to shove, we would be generally willing to defend Canada, Australia and NZ over anyone else, and then European countries at the next level. The reaction in support for Ukraine was pretty universal here and there are still lots of donations and support that is not shared with any African, Asian or Central/South American countries having similar problems.
Basically, you’re white so yes you can count on us!
I would highly recommend using docker compose files. The services you are after usually have them in their installation instructions, on github or docker hub (the latter tells you how many image pulls so you can see what most people are using). Also check out https://awesome-docker-compose.com/apps and https://haxxnet.github.io/Compose-Examples/.
Then think of each compose file as a separate service that functions completely independently and can’t access any others unless you open a port to the host system (ports: ) or have a common network (networks:). The container cannot access or save files unless you open volumes (volumes: ). Personally I have separate folders for each service, and always persist and store config, data and db files in a subfolder of that so it’s all in one place. It’s easier to migrate or save your info if something goes wrong, and males backups easier to manage.
In the composer file there is image: <image place/image>:<tag> The tag could be ‘latest’ or a specific version you can look up on docker hub by searching for that image and looking a the tags that are near the ‘latest’ tag or have the same file size. For critical services use a specific version, and for non critical use latest.
To update a docker compose file, go to the folder, update the version of the image (e.g :15.6 to :16.1) or if using the ‘latest’ tag no need to change anything. Then run “docker compose down && docker compose pull && docker compose up -d” to update the services top the latest image.
I use wud https://github.com/getwud/wud about once a week to highlight any available updates then manually update them one by one, and before doing so looking at the update notes to see if there are any breaking changes and testing the services after. I used to just use latest and blindly update but have had occasional issues like bad updates or having to figure out breaking changes. If it goes wrong you can just go back to the old version while you investigate more.
Also, docker keeps old images forever unless you prune them so lookup ‘docker image prune’ or ‘docker system prune’ before trying them as they’ll remove a lot.
If we rolled back a decade, Putin wasn’t around and something happened like idk, China invaded western Russia, I can imagine us helping Russia.
I should change it to “your population is mostly white so yes you can count on us”. I say this as an English born non-white person who has seen the differences in public reactions to Ukraine and other conflicts (Syria, various African ones, Gaza etc). Can’t say for certain it’s because of this reason but certainly feels like it!