Search
1000 results for “cli_ar”
-
FYI: Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ
-
ICYMI: Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ
-
Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ
-
ICYMI: Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ
-
Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ
-
Seattle’s Climate Pledge Arena switching to reusable cups from Portland startup - Beverage cups from Bold Reuse are collected and sanitized before being put back i... - https://www.geekwire.com/2025/seattles-climate-pledge-arena-switching-to-reusable-cups-from-portland-startup/ #climatepledgearena #foodandbeverage #sustainability #boldreuse
-
Seattle’s Climate Pledge Arena switching to reusable cups from Portland startup - Beverage cups from Bold Reuse are collected and sanitized before being put back i... - https://www.geekwire.com/2025/seattles-climate-pledge-arena-switching-to-reusable-cups-from-portland-startup/ #climatepledgearena #foodandbeverage #sustainability #boldreuse
-
Seattle’s Climate Pledge Arena switching to reusable cups from Portland startup - Beverage cups from Bold Reuse are collected and sanitized before being put back i... - https://www.geekwire.com/2025/seattles-climate-pledge-arena-switching-to-reusable-cups-from-portland-startup/ #climatepledgearena #foodandbeverage #sustainability #boldreuse
-
Seattle’s Climate Pledge Arena switching to reusable cups from Portland startup - Beverage cups from Bold Reuse are collected and sanitized before being put back i... - https://www.geekwire.com/2025/seattles-climate-pledge-arena-switching-to-reusable-cups-from-portland-startup/ #climatepledgearena #foodandbeverage #sustainability #boldreuse
-
Seattle’s Climate Pledge Arena switching to reusable cups from Portland startup - Beverage cups from Bold Reuse are collected and sanitized before being put back i... - https://www.geekwire.com/2025/seattles-climate-pledge-arena-switching-to-reusable-cups-from-portland-startup/ #climatepledgearena #foodandbeverage #sustainability #boldreuse
-
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated! -
@agowa338 if you refer to #OpenPGP cards here, have a look at the #ArchWiki article (and the upstream documentation) for the oct CLI: https://wiki.archlinux.org/title/OpenPGP-card-tools
-
This is a cool ❄️ story about a member of the #ecocommunity realice.eco working to restore Arctic sea ice and slow climate change: https://edition.cnn.com/2024/12/12/climate/refreeze-arctic-real-ice/index.html
-
I see people working on alternatives to rubygems.org.
I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.
I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.
First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.
Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.
I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.
I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.
My bigger concern is that the tools are under… let's say, uncertain control.
RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.
I'm afraid that any effort to take the development back to the community is futile because of this.
I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.
My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.
This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.
This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.
RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.
-
Happy Patch Tuesday from your friends at Fortinet. 13 security advisories, 15 vulnerabilities. No mention of exploitation in the wild:
- FG-IR-23-087 CVE-2023-45590 (9.6 critical) [FortiClient Linux] Remote Code Execution due to dangerous nodejs configuration
- FG-IR-23-345 CVE-2023-45588 and CVE-2024-31492 (8.2 high) FortiClientMac - Lack of configuration file validation
- FG-IR-23-419 CVE-2023-47542 (6.7 medium) FortiManager - Code Injection via Jinja Template
- FG-IR-23-288 CVE-2023-48785 (4.8 medium) FortiNAC-F - Lack of certificate validation
- FG-IR-23-413 CVE-2023-48784 (6.7 medium) FortiOS - Format String in CLI command
- FG-IR-23-224 CVE-2024-23662 (5.3 medium ) FortiOS - Web server ETag exposure
- FG-IR-23-493 CVE-2023-41677 (7.5 high) FortiOS & FortiProxy - administrator cookie leakage
- FG-IR-23-454 CVE-2024-23671 (8.1 high) FortiSandbox - Arbitrary file delete on endpoint
- FG-IR-24-060 CVE-2024-31487 (5.9 medium) FortiSandbox - Arbitrary file read on endpoint
- FG-IR-23-416 CVE-2023-47541 (6.7 medium) FortiSandbox - Arbitrary file write on CLI leading to arbitrary code execution
- FG-IR-23-411 CVE-2023-47540 (6.7 medium) FortiSandbox - Command injection impacting CLI command
- FG-IR-23-489 CVE-2024-21755 and CVE-2024-21756 (8.8 high) FortiSandbox - OS command injection on endpoint
- FG-IR-24-009 CVE-2024-26014 (5.3 medium) SMTP Smuggling (analyst note: third party vulnerability)
#PatchTuesday #Fortinet #FortiManager #vulnerability #FortiSandbox #FortiOS #FortiProxy
-
Hoarder v0.31.0 is out with big updates for developers! 🚀
The new Model Context Protocol (MCP) server means your AI tools can now "talk" to your bookmarks. Plus, the official CLI and SDK are finally here for programmatic access.
- AI integration via MCP server
- Official CLI/SDK for automation
- Enhanced browser extensionRelease: https://github.com/karakeep-app/karakeep/releases/tag/sdk%2Fv0.31.0
Run it on PikaPods: https://pikapods.com/pods?run=hoarder -
Hoarder v0.31.0 is out with big updates for developers! 🚀
The new Model Context Protocol (MCP) server means your AI tools can now "talk" to your bookmarks. Plus, the official CLI and SDK are finally here for programmatic access.
- AI integration via MCP server
- Official CLI/SDK for automation
- Enhanced browser extensionRelease: https://github.com/karakeep-app/karakeep/releases/tag/sdk%2Fv0.31.0
Run it on PikaPods: https://pikapods.com/pods?run=hoarder -
Hoarder v0.31.0 is out with big updates for developers! 🚀
The new Model Context Protocol (MCP) server means your AI tools can now "talk" to your bookmarks. Plus, the official CLI and SDK are finally here for programmatic access.
- AI integration via MCP server
- Official CLI/SDK for automation
- Enhanced browser extensionRelease: https://github.com/karakeep-app/karakeep/releases/tag/sdk%2Fv0.31.0
Run it on PikaPods: https://pikapods.com/pods?run=hoarder -
Hoarder v0.31.0 is out with big updates for developers! 🚀
The new Model Context Protocol (MCP) server means your AI tools can now "talk" to your bookmarks. Plus, the official CLI and SDK are finally here for programmatic access.
- AI integration via MCP server
- Official CLI/SDK for automation
- Enhanced browser extensionRelease: https://github.com/karakeep-app/karakeep/releases/tag/sdk%2Fv0.31.0
Run it on PikaPods: https://pikapods.com/pods?run=hoarder -
Hoarder v0.31.0 is out with big updates for developers! 🚀
The new Model Context Protocol (MCP) server means your AI tools can now "talk" to your bookmarks. Plus, the official CLI and SDK are finally here for programmatic access.
- AI integration via MCP server
- Official CLI/SDK for automation
- Enhanced browser extensionRelease: https://github.com/karakeep-app/karakeep/releases/tag/sdk%2Fv0.31.0
Run it on PikaPods: https://pikapods.com/pods?run=hoarder -
I see people working on alternatives to rubygems.org.
I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.
I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.
First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.
Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.
I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.
I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.
My bigger concern is that the tools are under… let's say, uncertain control.
RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.
I'm afraid that any effort to take the development back to the community is futile because of this.
I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.
My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.
This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.
This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.
RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.
-
I see people working on alternatives to rubygems.org.
I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.
I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.
First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.
Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.
I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.
I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.
My bigger concern is that the tools are under… let's say, uncertain control.
RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.
I'm afraid that any effort to take the development back to the community is futile because of this.
I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.
My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.
This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.
This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.
RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.
-
I see people working on alternatives to rubygems.org.
I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.
I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.
First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.
Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.
I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.
I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.
My bigger concern is that the tools are under… let's say, uncertain control.
RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.
I'm afraid that any effort to take the development back to the community is futile because of this.
I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.
My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.
This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.
This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.
RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.
-
I see people working on alternatives to rubygems.org.
I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.
I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.
First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.
Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.
I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.
I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.
My bigger concern is that the tools are under… let's say, uncertain control.
RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.
I'm afraid that any effort to take the development back to the community is futile because of this.
I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.
My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.
This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.
This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.
RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.
-
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated! -
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated! -
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated! -
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated! -
When two Hetzner servers died at the same time
On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same
pacman -Syyuthe day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back.nmap -Pn -p 22showedfilteredfrom anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.Several hours went into hypotheses that turned out to be wrong:
- The
encryptsshinitcpio hook referencing a/usr/lib/initcpio/udev/11-dm-initramfs.rulesfile that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway. PermitRootLogin noinsshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd showsclosed, notfiltered.- Predictable interface-naming drift after the systemd 260 upgrade. Patched the
.networkconfig to match by MAC. Useful hardening; not the cause. - Stale GRUB stage1 +
core.imgin the MBR. Arch never re-runsgrub-installafter agrubpackage upgrade. Refreshed it. Still filtered. - Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.
The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before
systemd-journaldcould flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.What it almost certainly was
Hetzner Dedicated servers configure the initramfs network with
ip=dhcpon the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:- Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
- New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays
filtered.
Hetzner’s own documentation has been quietly moving away from
ip=dhcptoward static IPv4 in the kernel command line. The fix is exactly that:GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"One line in
/etc/default/grub,grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.Why it matters for anyone running this stack
If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the
ip=dhcpshipped byinstallimageis a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routinepacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.Tooling
While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (
hal) — includinghal fix static-ip, which derives the static cmdline directly from your existingsystemd-networkd.networkfile:→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original
#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd/etc/default/grubis backed up to.hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you. - The
-
When two Hetzner servers died at the same time
On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same
pacman -Syyuthe day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back.nmap -Pn -p 22showedfilteredfrom anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.Several hours went into hypotheses that turned out to be wrong:
- The
encryptsshinitcpio hook referencing a/usr/lib/initcpio/udev/11-dm-initramfs.rulesfile that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway. PermitRootLogin noinsshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd showsclosed, notfiltered.- Predictable interface-naming drift after the systemd 260 upgrade. Patched the
.networkconfig to match by MAC. Useful hardening; not the cause. - Stale GRUB stage1 +
core.imgin the MBR. Arch never re-runsgrub-installafter agrubpackage upgrade. Refreshed it. Still filtered. - Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.
The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before
systemd-journaldcould flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.What it almost certainly was
Hetzner Dedicated servers configure the initramfs network with
ip=dhcpon the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:- Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
- New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays
filtered.
Hetzner’s own documentation has been quietly moving away from
ip=dhcptoward static IPv4 in the kernel command line. The fix is exactly that:GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"One line in
/etc/default/grub,grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.Why it matters for anyone running this stack
If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the
ip=dhcpshipped byinstallimageis a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routinepacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.Tooling
While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (
hal) — includinghal fix static-ip, which derives the static cmdline directly from your existingsystemd-networkd.networkfile:→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original
#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd/etc/default/grubis backed up to.hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you. - The