Limitations: Difference between revisions
From Nest Wiki
More actions
No edit summary |
U0A546Y17DK (talk | contribs) mNo edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
* you cannot mount a SMB, CIFS or NFS share | * you cannot mount a SMB, CIFS or NFS share | ||
* you do not get a public ipv4 (but we have a reverse proxy for http(s)), only a public ipv6 | * you do not get a public ipv4 (but we have a reverse proxy for http(s)), only a public ipv6 | ||
* containers have 2 cores, 2GB memory and 16GB storage by default, but you can | * containers have 2 cores, 2GB memory and 16GB storage by default, but you can request more [https://forms.hackclub.com/nest-resources here] | ||
* nest cannot guarantee an SLA, but we are working as hard as we can to keep the uptime as close to 100% as possible | * nest cannot guarantee an SLA, but we are working as hard as we can to keep the uptime as close to 100% as possible | ||
* access to /dev/net/tun (required for some things like wireguard) is disabled by default, but might be granted on request | * access to /dev/net/tun (required for some things like wireguard) is disabled by default, but might be granted on request | ||
Latest revision as of 19:18, 24 May 2026
Due to the nature of nest, there are several things that are not possible on nest (unfinished list):
- you cannot mount a SMB, CIFS or NFS share
- you do not get a public ipv4 (but we have a reverse proxy for http(s)), only a public ipv6
- containers have 2 cores, 2GB memory and 16GB storage by default, but you can request more here
- nest cannot guarantee an SLA, but we are working as hard as we can to keep the uptime as close to 100% as possible
- access to /dev/net/tun (required for some things like wireguard) is disabled by default, but might be granted on request