@Neoon can help to check on the alpine config when you are free?
Running free -h reports the host's memory in alpine, not the guest alpine OS, while cat /sys/fs/cgroup/memory.max shows the memory correctly. Probably some config issue or some weirdness with Alpine itself...
lxc5d7a7b88:~# free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 535.7M 361.3M 1.4G 246.5M
Swap: 0 0 0
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.max
268435456
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.current
27455488
I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.
@somik said: @Neoon can help to check on the alpine config when you are free?
Running free -h reports the host's memory in alpine, not the guest alpine OS, while cat /sys/fs/cgroup/memory.max shows the memory correctly. Probably some config issue or some weirdness with Alpine itself...
lxc5d7a7b88:~# free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 535.7M 361.3M 1.4G 246.5M
Swap: 0 0 0
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.max
268435456
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.current
27455488
Some applications show incorrect memory usage in containers.
Not something I know I can fix.
I got a reply on my second ticket, this time it wasn't auto closed.
Apparently its fixed but the VM is still down, I can't access their website right now, so I can't check anything.
According to them, they lost track of the ticket.
I got a reply on my second ticket, this time it wasn't auto closed.
Apparently its fixed but the VM is still down, I can't access their website right now, so I can't check anything.
According to them, they lost track of the ticket.
Anyway, I keep you updated.
"Sorry, too busy bombing Afghanistan and lost track of your ticket".
PK is back online since about 2 days.
I missed the email from hetrix, however I got a Ticket response yesterday.
Someone or something fixed PK, but I don't know who, the Support that replied yesterday denies any allegations.
Basically they just replied that the VM is working and Online, as far as I know last time I checked I couldn't even boot it.
Anyway, enjoy your PK containers everyone.
I am unsure at this point if I gonna enable deployments on PK again.
The Console is currently still broken, I dislike most "fixes", I don't have a propper non hacky solution yet.
As stated in previously sent emails, as part of migration of Japan services to our new infrastructure at Equinix TY8 location, the following changes will be applied with regard to IPv6 addresses assigned to existing services:
• All of the services will automatically receive one dedicated routed /48 IPv6 prefix (once the migration is completed on 22nd April 2026).
Also
Maintenance Window:
Start Time: 1 AM 22nd April 2026 (Japan time)
Completion Time: 7 AM 22nd April (Japan time)
Impact: Service will be inaccessible during the migration phase (depending on disk size it can take 5 to 30 minutes per service)
@Neoon my Islamabad/PK container cannot be rebooted regardless of me trying from the Dashboard or from the Shell can you check? It is still online & accessible though!
Ah: stopping and starting the container worked!
@jcn50 said: @Neoon my Islamabad/PK container cannot be rebooted regardless of me trying from the Dashboard or from the Shell can you check? It is still online & accessible though!
Ah: stopping and starting the container worked!
You have been rebooting it successfully, according to logs, neither do I have issues rebooting.
What is the issue?
I have a service that starts @ boot time, and whatever I tried it did not start:
Dashboard Restart button
Dashboard Stop + Start buttons
Shell console reboot command
The uptime command gives the uptime of the host~ not of the container.
Still, I don't understand what your issue is, your container rebooted fine.
Yes some tools might give you different info depending on what and what os you are using.
@Neoon said: The Subnet in JP is ready and configured.
Thank you, I'm glad it has IPv6 now.
Here is a minor problem in Tokyo Equinix node however, when I try to install Arch Linux OS to a LXC VPS, the control panel prompted success and the IPv6 is reachable via ping, but SSH failed, and the port seems not open (I tried nmap -6 -p 22 IPV6-ADDRESS).
In the past, I found sshd in Arch Linux is not enabled via systemd, but since console or shell worked in the control panel, I could manually enable it there, but now console or shell seem not working on my side either. By the way, Debian OS works perfectly. Thank you.
@somik said: @Neoon can help to check on the alpine config when you are free?
Running free -h reports the host's memory in alpine, not the guest alpine OS, while cat /sys/fs/cgroup/memory.max shows the memory correctly. Probably some config issue or some weirdness with Alpine itself...
lxc5d7a7b88:~# free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 535.7M 361.3M 1.4G 246.5M
Swap: 0 0 0
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.max
268435456
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.current
27455488
@jcn50 said: The uptime command gives the uptime of the host~ not of the container.
@Neoon said: The Subnet in JP is ready and configured.
Thank you, I'm glad it has IPv6 now.
Here is a minor problem in Tokyo Equinix node however, when I try to install Arch Linux OS to a LXC VPS, the control panel prompted success and the IPv6 is reachable via ping, but SSH failed, and the port seems not open (I tried nmap -6 -p 22 IPV6-ADDRESS).
In the past, I found sshd in Arch Linux is not enabled via systemd, but since console or shell worked in the control panel, I could manually enable it there, but now console or shell seem not working on my side either. By the way, Debian OS works perfectly. Thank you.
its always DNS, the IPv6 of the node changed but nginx cached the DNS response, fixed.
@somik said: @Neoon can help to check on the alpine config when you are free?
Running free -h reports the host's memory in alpine, not the guest alpine OS, while cat /sys/fs/cgroup/memory.max shows the memory correctly. Probably some config issue or some weirdness with Alpine itself...
lxc5d7a7b88:~# free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 535.7M 361.3M 1.4G 246.5M
Swap: 0 0 0
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.max
268435456
lxc5d7a7b88:~# cat /sys/fs/cgroup/memory.current
27455488
@jcn50 said: The uptime command gives the uptime of the host~ not of the container.
Yea, nah, its disabled by default for a reason.
Its a nice feature to allow a container to display the correct memory usage.
However it requires a elevated process on the node to respond, which is limited of course but, nah.
Comments
Comparing it to Virmach, its actually fast.
Free NAT KVM | Free NAT LXC
NZ connectivity issues on IPv4 should be solved too.
Ticket took a bit to find the cause.
Free NAT KVM | Free NAT LXC
Just a short PSA, I was busy.
Yes PK is down, and yes its down since yesterday.
Ticket is open since yesterday, they are still working on a resolution.
Free NAT KVM | Free NAT LXC
They are away to celibate CNY (cause right after that, month of Ramadan starts)
Unfortunately, I do not meet these requirements.
@Neoon can help to check on the alpine config when you are free?
Running
free -hreports the host's memory in alpine, not the guest alpine OS, whilecat /sys/fs/cgroup/memory.maxshows the memory correctly. Probably some config issue or some weirdness with Alpine itself...Some applications show incorrect memory usage in containers.
Not something I know I can fix.
Free NAT KVM | Free NAT LXC
NZ is available again.
New packages for NZ should be released tomorraw.
Other locations will be restocked this week, if possible.
Free NAT KVM | Free NAT LXC
New Packages are live, Storage has been increased up to 10GB.
Free NAT KVM | Free NAT LXC
Update on PK:
I got a reply on my second ticket, this time it wasn't auto closed.
Apparently its fixed but the VM is still down, I can't access their website right now, so I can't check anything.
According to them, they lost track of the ticket.
Anyway, I keep you updated.
Free NAT KVM | Free NAT LXC
"Sorry, too busy bombing Afghanistan and lost track of your ticket".
Restocked: Tokyo, Singapore, Bratislava and Valdivia
Free NAT KVM | Free NAT LXC
FYI, alpine linux does not "shutdown" with the "Stop" button in panel, probably cause alpine uses
poweroffinstead of the standardshutdown -h 0PK is back online since about 2 days.
I missed the email from hetrix, however I got a Ticket response yesterday.
Someone or something fixed PK, but I don't know who, the Support that replied yesterday denies any allegations.
Basically they just replied that the VM is working and Online, as far as I know last time I checked I couldn't even boot it.
Anyway, enjoy your PK containers everyone.
I am unsure at this point if I gonna enable deployments on PK again.
The Console is currently still broken, I dislike most "fixes", I don't have a propper non hacky solution yet.
Free NAT KVM | Free NAT LXC
The console issue has been fixed, sorry that it took so long.
The patch included security fixes, so I could not hesitate updating incus/lxd.
Free NAT KVM | Free NAT LXC
Tokyo is getting its prefix, tomorraw.
As stated in previously sent emails, as part of migration of Japan services to our new infrastructure at Equinix TY8 location, the following changes will be applied with regard to IPv6 addresses assigned to existing services:
• All of the services will automatically receive one dedicated routed /48 IPv6 prefix (once the migration is completed on 22nd April 2026).
Also
Maintenance Window:
Start Time: 1 AM 22nd April 2026 (Japan time)
Completion Time: 7 AM 22nd April (Japan time)
Impact: Service will be inaccessible during the migration phase (depending on disk size it can take 5 to 30 minutes per service)
Free NAT KVM | Free NAT LXC
And the SG dedicated server I got from oneprovider just gives a /128 IPv6 and they say they can't even add additional IPv6 IPs to the server...
Oh well, IPv6 adoption amongst the provider is still very poor...
@Neoon my Islamabad/PK container cannot be rebooted regardless of me trying from the Dashboard or from the Shell
can you check? It is still online & accessible though!
Ah: stopping and starting the container worked!
💩 VirCrap 💩
You have been rebooting it successfully, according to logs, neither do I have issues rebooting.
What is the issue?
Free NAT KVM | Free NAT LXC
I have a service that starts @ boot time, and whatever I tried it did not start:
rebootcommandThe
uptimecommand gives the uptime of the host~ not of the container.💩 VirCrap 💩
Nevermind: everything seems to be working fine now! Sorry for the bother!
💩 VirCrap 💩
Still, I don't understand what your issue is, your container rebooted fine.
Yes some tools might give you different info depending on what and what os you are using.
Free NAT KVM | Free NAT LXC
I also added PK back in stock, since it has been stable the last 3 weeks.
Free NAT KVM | Free NAT LXC
The Subnet in JP is ready and configured.
I will do a quick reboot tomorrow and enable IPv6 afterwards.
As soon its available, just press reconfigure in the panel.
Free NAT KVM | Free NAT LXC
Done.
Free NAT KVM | Free NAT LXC
Thank you, I'm glad it has IPv6 now.
Here is a minor problem in Tokyo Equinix node however, when I try to install Arch Linux OS to a LXC VPS, the control panel prompted success and the IPv6 is reachable via ping, but SSH failed, and the port seems not open (I tried nmap -6 -p 22 IPV6-ADDRESS).
In the past, I found sshd in Arch Linux is not enabled via systemd, but since console or shell worked in the control panel, I could manually enable it there, but now console or shell seem not working on my side either. By the way, Debian OS works perfectly. Thank you.
MicroLXC is lovable. Uptime of C1V
This is because Alpine relies on sysinfo for that information.
To fix it you have to set
security.syscalls.intercept.sysinfo=trueunder the instance setting for each Alpine container and restart itreference:
Instance options - Security policies - security.syscalls.intercept.sysinfo
its always DNS, the IPv6 of the node changed but nginx cached the DNS response, fixed.
Free NAT KVM | Free NAT LXC
Yea, nah, its disabled by default for a reason.
Its a nice feature to allow a container to display the correct memory usage.
However it requires a elevated process on the node to respond, which is limited of course but, nah.
Free NAT KVM | Free NAT LXC
Lads and Gents, we got a new Node in Ho Chi Minh.
Courtesy of Onidel, thanks @oloke
/64 routed iPv6, HAPorxy, DNS Proxy the usual.
Free NAT KVM | Free NAT LXC