This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
manuals:vps:vpsadminos [2018/09/30 13:11] – Removed network configuration Aither | manuals:vps:vpsadminos [2019/11/10 11:04] – mounts -> exports Aither | ||
---|---|---|---|
Line 61: | Line 61: | ||
UID/GID maps for VPS and NAS datasets, which will let each member to isolate | UID/GID maps for VPS and NAS datasets, which will let each member to isolate | ||
his own VPS and yet share some chosen range of user/group IDs. | his own VPS and yet share some chosen range of user/group IDs. | ||
- | |||
- | The user namespace significantly changes how you can share data between VPS | ||
- | and NAS. At the moment, it is **not possible** to mount NAS to a VPS running | ||
- | on a vpsAdminOS node so that you'd have access to the data. This will become | ||
- | possible when custom UID/GID maps are properly implemented. | ||
==== General ==== | ==== General ==== | ||
Changes regarding VPS, but independent on the distribution used: | Changes regarding VPS, but independent on the distribution used: | ||
- | * ''/ | + | * ''/ |
- | * ''/ | + | |
* Swap is not shown in ''/ | * Swap is not shown in ''/ | ||
- | * '' | ||
==== Debian/ | ==== Debian/ | ||
Line 83: | Line 76: | ||
===== Behaviour changes in vpsAdmin ===== | ===== Behaviour changes in vpsAdmin ===== | ||
+ | * NAS and snapshots are not accessed using vpsAdmin [[manuals: | ||
* Reinstalling VPS on vpsAdminOS no longer deletes subdatasets and does not reset its configuration to the initial state, e.g. VPS features remain as they were. | * Reinstalling VPS on vpsAdminOS no longer deletes subdatasets and does not reset its configuration to the initial state, e.g. VPS features remain as they were. | ||
* VPS features: bridge, iptables and NFS aren't configurable, | * VPS features: bridge, iptables and NFS aren't configurable, | ||
Line 99: | Line 93: | ||
resources among 4 VPS. | resources among 4 VPS. | ||
- | It is not possible to clone or swap production VPS with VPS in the staging | + | You can either create a new VPS or clone an existing |
- | environment. Migration | + | All mounts are removed when cloning, because NAS isn't acessible as of yet, |
- | Access to the NAS is also restricted, | + | see [[# |
==== Supported distributions ==== | ==== Supported distributions ==== | ||
- | * Alpine 3.6, 3.7 | + | * Alpine 3.8, 3.9 |
* Arch | * Arch | ||
- | * CentOS 7.5 | + | * CentOS 7, 8 |
- | * Debian | + | * Debian 9, 10 |
- | * Fedora | + | * Fedora |
* Gentoo | * Gentoo | ||
* NixOS | * NixOS | ||
+ | * openSUSE Leap 15.1, Tumbleweed | ||
+ | * Slackware 14.2 | ||
* Ubuntu 16.04, 18.04 | * Ubuntu 16.04, 18.04 | ||
- | + | * Void Linux | |
- | ==== Other distributions ==== | + | |
- | + | ||
- | In case your distribution isn't supported yet, you can help us make | + | |
- | it happen, or wait until someone does it for you, see | + | |
- | [[https:// | + | |
- | + | ||
- | Distribution templates installable from vpsAdmin are built using scripts at | + | |
- | [[https:// | + | |
- | If your distribution isn't there, it has to be added. | + | |
- | + | ||
- | When the built script is done, it is necessary to add support for your | + | |
- | distribution into '' | + | |
- | resolvers, etc., see [[https:// | + | |
==== Features ==== | ==== Features ==== | ||
Line 134: | Line 117: | ||
{{ : | {{ : | ||
- | * Docker (experimental) - Enables | + | * Docker (experimental) - Enables support for Docker. |
* FUSE - " | * FUSE - " | ||
* KVM - " | * KVM - " |