WARN Exec socket appeared but heartbeat failed, exec will not be available

[colorfulshark]

Hi guys,

I would like to use this project as a light weight sandbox, but had some trouble running the example.

I installed the binaries with

cp a3s* lib /usr/local/bin
ln -s /usr/local/bin/lib/libkrunfw.so* /usr/local/lib/

And when I try to launch the very start box, It outputted some error log

root@ai45lab:~# a3s-box run --name hello alpine:latest -- echo "Hello from MicroVM"
Creating box hello (a143eb40fcda)...
2026-04-21T07:34:20.157417Z  WARN Exec socket appeared but heartbeat failed, exec will not be available
Box hello (a143eb40fcda) started. Press Ctrl-C to stop.
init.krun: entered main argc=1
init.krun: mount_filesystems ok
init.krun: after cmdline env import KRUN_INIT=/sbin/init KRUN_INIT_PID1=<null> BOX_EXEC_EXEC=echo
init.krun: root propagation ok
init.krun: tty/session configured
init.krun: config parsed
init.krun: selected exec=/sbin/init init_pid1=0
init.krun: setup_redirects ok
init.krun: execvp(/sbin/init) starting
init.krun: execvp(/sbin/init) failed errno=2
Couldn't execute '/sbin/init' inside the vm: No such file or directory

Stopping box hello...
Box hello stopped.

I also tried running a box with interactive shell, still got errors

root@ai45lab:~# a3s-box run -it --name dev alpine:latest -- /bin/sh
Creating box dev (3a4989f02274)...
2026-04-21T07:47:58.636724Z  WARN Exec socket appeared but heartbeat failed, exec will not be available
Error: Exec error: Failed to connect to PTY server at /root/.a3s/boxes/3a4989f0-2274-4ef8-bef1-26a645a81af2/sockets/pty.sock: Connection refused (os error 111)

Appreciate for your help.

[ZhiXiao-Lin]

Hi, thanks for reporting this issue. To help diagnose the root cause, could you please provide the following information:

System Information

1. Machine type — What CPU architecture? (e.g., x86_64, aarch64)
2. Host OS — What Linux distribution and version are you running on? (e.g., Ubuntu 22.04, Debian 12)
3. a3s-box version — What version of a3s-box are you using?

   a3s-box --version

Installation Details

4. How did you install a3s-box? (from source, binary release, homebrew, etc.)

5. **What's the full contents of your /usr/local/bin and /usr/local/lib directories?

   ls -la /usr/local/bin/a3s* /usr/local/lib/libkrun* 2>/dev/null

6. **Is the guest init binary present?

   find /usr/local/bin -name \"*guest-init*\" 2>/dev/null
   # Also check in lib dir
   find /usr/local/lib -name \"*guest-init*\" 2>/dev/null

Debugging

7. Can you run with verbose debug logging? Try:

   RUST_LOG=debug a3s-box run --name hello alpine:latest -- echo \"Hello\"

8. Check if the rootfs was built correctly — look for the box directory that was created:

   ls -la ~/.a3s/boxes/*/rootfs/sbin/init 2>/dev/null
   file ~/.a3s/boxes/*/rootfs/sbin/init 2>/dev/null

9. What does `strace` show? If available:

   strace -f a3s-box run --name hello alpine:latest -- echo \"Hello\" 2>&1 | grep -E \"(execve|sbin/init|BOX_EXEC)\" | head -30

This will help determine whether:

• The guest init binary is missing from your installation
• The guest init is not being installed into the rootfs
• The `BOX_EXEC_EXEC` environment variable is not being passed correctly to the VM

[colorfulshark]

Hi, thanks for reporting this issue. To help diagnose the root cause, could you please provide the following information:

System Information

1. Machine type — What CPU architecture? (e.g., x86_64, aarch64)
2. Host OS — What Linux distribution and version are you running on? (e.g., Ubuntu 22.04, Debian 12)
3. a3s-box version — What version of a3s-box are you using?
   a3s-box --version

CPU: AMD Ryzen H255
Host OS: Debian 13
a3s-box version: 2.0.0

Installation Details

4. How did you install a3s-box? (from source, binary release, homebrew, etc.)
   Download binary from github release and install manually.
5. What's the full contents of your /usr/local/bin and /usr/local/lib directories?
   ls -la /usr/local/bin/a3s /usr/local/lib/libkrun 2>/dev/null

root@ai45lab:~#  ls -la /usr/local/bin/a3s* /usr/local/lib/libkrun* 2>/dev/null
-rwxr-xr-x 1 root root 23345633 Apr 21 07:32 /usr/local/bin/a3s-box
-rwxr-xr-x 1 root root 15669697 Apr 21 07:32 /usr/local/bin/a3s-box-cri
-rwxr-xr-x 1 root root  5165632 Apr 21 07:32 /usr/local/bin/a3s-box-guest-init
-rwxr-xr-x 1 root root  4457417 Apr 21 07:32 /usr/local/bin/a3s-box-shim
-rwxr-xr-x 1 root root  5538225 Apr 21 06:35 /usr/local/lib/libkrun.so
-rwxr-xr-x 1 root root  5538225 Apr 21 06:35 /usr/local/lib/libkrun.so.1
-rwxr-xr-x 1 root root  5538225 Apr 21 06:35 /usr/local/lib/libkrun.so.1.17.0
lrwxrwxrwx 1 root root       31 Apr 21 07:33 /usr/local/lib/libkrunfw.so -> /usr/local/bin/lib/libkrunfw.so
lrwxrwxrwx 1 root root       33 Apr 21 07:33 /usr/local/lib/libkrunfw.so.5 -> /usr/local/bin/lib/libkrunfw.so.5

6. **Is the guest init binary present?
   find /usr/local/bin -name "guest-init" 2>/dev/null

root@ai45lab:~# find /usr/local/bin -name "*guest-init*" 2>/dev/null
/usr/local/bin/a3s-box-guest-init

Also check in lib dir

find /usr/local/lib -name "guest-init" 2>/dev/null

root@ai45lab:~# find /usr/local/bin -name "*guest-init*" 2>/dev/null
/usr/local/bin/a3s-box-guest-init

root@ai45lab:~# find /usr/local/lib -name "guest-init" 2>/dev/null
root@ai45lab:~# 

Debugging

7. Can you run with verbose debug logging? Try:
   RUST_LOG=debug a3s-box run --name hello alpine:latest -- echo "Hello"

Too many logs but end with
[2026-04-21T09:28:55Z DEBUG vmm] using vmm exit code: 127
[2026-04-21T09:28:55Z INFO  vmm] Vmm is stopping.
2026-04-21T09:28:56.105809Z DEBUG vm_boot{box_id=781ec7fe-754c-46eb-ace0-6cb62781777f}:wait_for_ready: VM process is running
2026-04-21T09:28:56.105851Z DEBUG vm_boot{box_id=781ec7fe-754c-46eb-ace0-6cb62781777f}:wait_for_ready: Waiting for exec server socket socket_path=/root/.a3s/boxes/781ec7fe-754c-46eb-ace0-6cb62781777f/sockets/exec.sock
2026-04-21T09:28:56.105887Z DEBUG vm_boot{box_id=781ec7fe-754c-46eb-ace0-6cb62781777f}:wait_for_ready: Exec socket file detected
2026-04-21T09:28:56.105963Z DEBUG vm_boot{box_id=781ec7fe-754c-46eb-ace0-6cb62781777f}:wait_for_ready: Exec connect failed, retrying error=Exec error: Failed to connect to exec server at /root/.a3s/boxes/781ec7fe-754c-46eb-ace0-6cb62781777f/sockets/exec.sock: Connection refused (os error 111)

8. Check if the rootfs was built correctly — look for the box directory that was created:
   ls -la ~/.a3s/boxes/*/rootfs/sbin/init 2>/dev/null

root@ai45lab:~# ls -la ~/.a3s/boxes/*/rootfs/sbin/init 2>/dev/null
-rwxr-xr-x 1 root root 5338136 Apr 21 06:26 /root/.a3s/boxes/02245875-3cfe-481e-930c-d9c6b7a8ac61/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 06:35 /root/.a3s/boxes/157b339a-fac1-42b7-b136-445e1ac08ea2/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 07:47 /root/.a3s/boxes/3a4989f0-2274-4ef8-bef1-26a645a81af2/rootfs/sbin/init
-rwxr-xr-x 1 root root 5165632 Apr 21 06:30 /root/.a3s/boxes/50d12f99-f2d1-4b83-99ee-965d63614c55/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 09:28 /root/.a3s/boxes/77f493d4-9c1a-4526-9b31-67232e6185a7/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 09:28 /root/.a3s/boxes/781ec7fe-754c-46eb-ace0-6cb62781777f/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 06:29 /root/.a3s/boxes/a5c81bda-b5fa-4981-a588-12d412a42f49/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 09:17 /root/.a3s/boxes/c20851dd-8164-41c4-af7f-232f9b591ad3/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 09:17 /root/.a3s/boxes/e9637925-cbc4-40ff-91d6-bb0b163686bc/rootfs/sbin/init
-rwxr-xr-x 1 root root 5338136 Apr 21 09:28 /root/.a3s/boxes/f99ea77d-3ee5-4836-90ac-31be5980a983/rootfs/sbin/init

file ~/.a3s/boxes/*/rootfs/sbin/init 2>/dev/null

/root/.a3s/boxes/02245875-3cfe-481e-930c-d9c6b7a8ac61/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/157b339a-fac1-42b7-b136-445e1ac08ea2/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/3a4989f0-2274-4ef8-bef1-26a645a81af2/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/50d12f99-f2d1-4b83-99ee-965d63614c55/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, BuildID[sha1]=fbc9fdc0af3584321e0f60e54899e6255e2d59db, not stripped
/root/.a3s/boxes/77f493d4-9c1a-4526-9b31-67232e6185a7/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/781ec7fe-754c-46eb-ace0-6cb62781777f/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/a5c81bda-b5fa-4981-a588-12d412a42f49/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/c20851dd-8164-41c4-af7f-232f9b591ad3/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/e9637925-cbc4-40ff-91d6-bb0b163686bc/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped
/root/.a3s/boxes/f99ea77d-3ee5-4836-90ac-31be5980a983/rootfs/sbin/init: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=843eb736ca1b3963d8fc1c112e144341b6860d96, not stripped

9. What does strace show? If available:
   strace -f a3s-box run --name hello alpine:latest -- echo "Hello" 2>&1 | grep -E "(execve|sbin/init|BOX_EXEC)" | head -30

no output

This will help determine whether:

• The guest init binary is missing from your installation
• The guest init is not being installed into the rootfs
• The BOX_EXEC_EXEC environment variable is not being passed correctly to the VM

[ZhiXiao-Lin]

Root Cause Analysis

This issue had two distinct root causes:

1. wait_for_children() exits too early (causes both errors)

In guest-init/src/main.rs, the wait_for_children() function called process::exit() immediately when the container process exited. However, the vsock servers (exec, PTY, attestation) run as background threads started AFTER the container process spawns. When the container process exited quickly (e.g. echo "Hello" completes in milliseconds), the entire VM was terminated before the vsock servers had a chance to start - hence the WARN Exec socket appeared but heartbeat failed and PTY connection refused errors.

2. Fallback Entrypoint /sbin/init does not exist in Alpine

When neither ENTRYPOINT nor CMD is set in the OCI image, the code fell back to /sbin/init. Alpine Linux does not have /sbin/init - it uses busybox init invoked differently. This caused the execvp(/sbin/init) failed errno=2 error.

Fixes Applied (v2.0.1)

Fix 1: VM stays alive until SIGTERM

The wait_for_children() function now loops indefinitely after the container process exits, until it receives a SIGTERM shutdown signal. This gives the vsock server threads time to start before the VM exits.

Before:

if pid == container_pid {
    process::exit(status);
}

After:

if pid == container_pid {
    loop {
        if SHUTDOWN_REQUESTED.load(Ordering::SeqCst) {
            graceful_shutdown(CHILD_SHUTDOWN_TIMEOUT_MS);
            return Ok(());
        }
        std::thread::sleep(std::time::Duration::from_secs(1));
    }
}

Fix 2: Fallback entrypoint changed from /sbin/init to /bin/sh

/bin/sh is universally available across all Linux distributions including Alpine.

Testing

All 787 runtime unit tests pass. The original failing command was verified:

a3s-box run alpine:latest -- echo "Hello from MicroVM"

Pull Request: #4
Release: v2.0.1 - https://github.com/AI45Lab/Box/releases/tag/v2.0.1

[huapox]

+1, with v2.0.7

[ZhiXiao-Lin]

Thanks for the v2.0.7 ping, @huapox — that report is consistent with what we found, and it turns out the original fix only partly survived.

Root cause (re-traced against v2.0.7):

There were two symptoms in the original report, with different fates:

1. execvp(/sbin/init) failed (Alpine has no /sbin/init) — fixed and still fixed: the OCI entrypoint fallback is /bin/sh.
2. WARN ... heartbeat failed / run -it Connection refused — regressed. The v2.0.1 fix kept the VM alive after the container exited so the exec/PTY vsock servers had time to come up; that keep-alive was reverted in v2.0.4 (it conflicted with clean container-exit / exit-code handling).

In v2.0.7 the readiness probe already bails out when the VM exits, so a fast-exiting container no longer warns. The residual case is a slow-but-alive cold boot: guest-init binds the exec (vsock 4089) and PTY (4090) servers only late in boot — after the virtio-fs pivot, network setup, and container spawn — and it can't start them earlier without forking the container while multi-threaded (which would risk a deadlock in the child). On a loaded host that bind can land past the host's fixed 10 s readiness budget → the warning, and for run -it the PTY attach loses the race.

Fix (#14): raise the host's exec-readiness budget to 30 s (it returns instantly once the heartbeat passes, and still bails the moment the VM exits, so nothing slow-paths a fast box), which also lets the subsequent run -it PTY attach connect; plus corrected the misleading warning wording. Verified on a Linux/KVM host — fast-exit boxes no longer warn and a long-lived box reports Exec server heartbeat passed + exec works.

Could you help confirm @huapox? To make sure 30 s actually covers your machine (rather than a different fault):

• Are you using default networking or --network <bridge>?
• Does exec/attach eventually work if you retry, or never?
• If you can, the tail of RUST_LOG=a3s_box_runtime::vm::ready=debug a3s-box run --rm alpine -- echo hi 2>&1 — specifically whether you see VM exited before exec server became ready vs the heartbeat warning.

That tells us whether you're hitting the timing race (which #14 fixes) or a hard never-bind (e.g. bridge eth0 setup failing), which would be a separate issue.

[ZhiXiao-Lin]

Update: the proper fix is now in #15 (superseding the interim #14). Instead of widening the readiness timeout, it makes boot wait for the actual readiness event bounded by VM liveness — so a slow cold boot no longer trips the warning regardless of how long it takes — and binds the exec/PTY vsock sockets early so an interactive -it attach can't be refused. Verified on Linux/KVM with a 15s-boot-delay before/after (old: warning at 10s + exec fails; new: no warning, exec works).

[huapox]

thx for the reply, with detail:

• network: default
• never work env tried: debian9, debian11 in two devices; self build with debian9.glibc224 also tried with v207 of org's release with ubuntu24 in container
  • same env, try with other rustApps with libkrun: microsandbox smolvm works
• debug, with follows

root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:01:14  
$ ./a3s-box -V
a3s-box 2.0.7

# try with ubuntu22 for guest os
root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |12:59:36  
$ ./a3s-box run -it --rm  registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--ubuntu---22.04 -- bash
Creating box mild_kernighan (fcca9c37370e)...
Pulling registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--ubuntu---22.04...
  [1/1] 90252a0c3adb: Pulling 28.2 MB...
  [1/1] 90252a0c3adb: 28.2 MB ✓
2026-06-11T05:00:52.049603Z  WARN VM exited before exec socket appeared
Error: Failed to connect to PTY server at /tmp/a3s-box-sockets/fcca9c37-370e-4a04-90c9-f590361aaf19/pty.sock after 10s: Exec error: Failed to connect to PTY server at /tmp/a3s-box-sockets/fcca9c37-370e-4a04-90c9-f590361aaf19/pty.sock: No such file or directory (os error 2)
root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:01:02  

# debug with RUST_LOG
root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:08:48  
$ alpine=registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--alpine---3.13
root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:08:53  
$ RUST_LOG=a3s_box_runtime::vm::ready=debug ./a3s-box run --rm $alpine -- echo hi 2>&1
Creating box agile_babbage (8fd8822091d3)...
2026-06-11T05:08:59.415464Z DEBUG Waiting for VM process to stabilize
2026-06-11T05:09:00.416330Z DEBUG VM process is running
2026-06-11T05:09:00.416393Z DEBUG Waiting for exec server socket socket_path=/tmp/a3s-box-sockets/8fd88220-91d3-4c6a-8e47-891ab3020c19/exec.sock
2026-06-11T05:09:00.416578Z  WARN VM exited before exec socket appeared
Box agile_babbage (8fd8822091d3) started. Press Ctrl-C to stop.
Box agile_babbage exited and was removed.

[huapox]

with full debug log

root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:17:37  
$ find /tmp/a3s-box-sockets/ 
/tmp/a3s-box-sockets/
$ ls -l /tmp/ |grep a3s
drwxr-xr-x 2 root root     4096 6月  11 13:16 a3s-box-sockets

$ #RUST_LOG=debug ./a3s-box run --rm $alpine -- /bin/bash
$ #RUST_LOG=a3s_box_runtime::vm::ready=debug ./a3s-box run --rm $alpine -- tail -f /dev/null
root @ debian in /_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64 |13:16:21  
$ RUST_LOG=debug ./a3s-box run --rm $alpine -- /bin/bash
2026-06-11T05:16:38.918288Z DEBUG Overlay mounted via mount(2) lower=/tmp/.tmpKiYBur/lower merged=/tmp/.tmpKiYBur/merged
2026-06-11T05:16:38.935536Z DEBUG Overlay unmounted path=/tmp/.tmpKiYBur/merged
2026-06-11T05:16:38.936032Z  INFO Using overlayfs rootfs provider
Creating box quick_dijkstra (05a0160902a2)...
2026-06-11T05:16:38.936152Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: Booting VM box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe
2026-06-11T05:16:38.973726Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Pulling OCI image from registry reference=registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--alpine---3.13
2026-06-11T05:16:38.976238Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Using cached image requested_reference=registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--alpine---3.13 matched_reference=registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--alpine---3.13 digest=sha256:b31b67a6a01595ce7d94655e951da933e1b58ca63f23d646e430e2ffa6ec33da
2026-06-11T05:16:38.976956Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Rootfs cache hit cache_key=82f7d21cf139 reference=registry.cn-shenzhen.aliyuncs.com/infrasync/v2025:library--alpine---3.13 provider="overlay"
2026-06-11T05:16:38.983273Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Overlay mounted via mount(2) lower=/root/.a3s/cache/rootfs/82f7d21cf13975dee74bc70ddb02ae02ae8112735775f495d35379054d3dec5c merged=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/merged
2026-06-11T05:16:38.983333Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Overlay mount ready lower=/root/.a3s/cache/rootfs/82f7d21cf13975dee74bc70ddb02ae02ae8112735775f495d35379054d3dec5c merged=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/merged
2026-06-11T05:16:38.988848Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Refreshing guest init on cached rootfs guest_init=/_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64/a3s-box-guest-init
2026-06-11T05:16:38.998078Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:prepare_layout: Installed guest init src=/_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64/a3s-box-guest-init dst=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/merged/sbin/init
2026-06-11T05:16:39.003126Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: Configured guest DNS dns=nameserver 192.168.216.209
nameserver 240e:47f:618:28c1::ae
2026-06-11T05:16:39.003415Z DEBUG Using guest init as PID 1 env=[("BOX_EXEC_EXEC", "/bin/bash"), ("BOX_EXEC_ARGC", "0"), ("BOX_EXEC_WORKDIR", "/workspace"), ("BOX_EXEC_ENV_PATH", "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"), ("A3S_SEC_SECCOMP", "default"), ("A3S_SEC_NO_NEW_PRIVS", "1")]
2026-06-11T05:16:39.003542Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:vm_start: Starting VM subprocess box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe vcpus=2 memory_mib=512
2026-06-11T05:16:39.004280Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:vm_start: Spawning shim subprocess shim=/_ext/down/ai_tools/_a3s/a3s-box-v2606-linux-x86_64/a3s-box-shim box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe
2026-06-11T05:16:39.004486Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:vm_start: Redirecting shim stdio to per-box files box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe stdout=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/logs/shim.stdout.log stderr=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/logs/shim.stderr.log
2026-06-11T05:16:39.005038Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:vm_start: Shim subprocess spawned box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe pid=11680
2026-06-11T05:16:39.005329Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:wait_for_ready: Waiting for VM process to stabilize
2026-06-11T05:16:40.007122Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:wait_for_ready: VM process is running
2026-06-11T05:16:40.007180Z DEBUG vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:wait_for_ready: Waiting for exec server socket socket_path=/tmp/a3s-box-sockets/05a01609-02a2-4c92-afb3-a0a5a21edafe/exec.sock
2026-06-11T05:16:40.007321Z  WARN vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}:wait_for_ready: VM exited before exec socket appeared
2026-06-11T05:16:40.007365Z  INFO vm_boot{box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: VM ready box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe
Box quick_dijkstra (05a0160902a2) started. Press Ctrl-C to stop.
2026-06-11T05:16:40.519268Z  INFO destroy_with_options{signal=15 timeout_ms=10000 box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: Destroying VM box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe signal=15 timeout_ms=10000
2026-06-11T05:16:40.519483Z DEBUG destroy_with_options{signal=15 timeout_ms=10000 box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: Sending stop signal to VM process pid=11680 box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe signal=15
2026-06-11T05:16:40.519558Z DEBUG destroy_with_options{signal=15 timeout_ms=10000 box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: VM process exited gracefully pid=11680 status=ExitStatus(unix_wait_status(32512))
2026-06-11T05:16:40.544452Z DEBUG destroy_with_options{signal=15 timeout_ms=10000 box_id=05a01609-02a2-4c92-afb3-a0a5a21edafe}: Overlay unmounted path=/root/.a3s/boxes/05a01609-02a2-4c92-afb3-a0a5a21edafe/merged
2026-06-11T05:16:40.548121Z DEBUG Failed to remove external socket directory path=/tmp/a3s-box-sockets/05a01609-02a2-4c92-afb3-a0a5a21edafe error=No such file or directory (os error 2)
2026-06-11T05:16:40.548336Z DEBUG Failed to remove external socket directory path=/tmp/a3s-box-sockets/05a01609-02a2-4c92-afb3-a0a5a21edafe error=No such file or directory (os error 2)
Box quick_dijkstra exited and was removed.