StorageD Crash in graphd-client connected from container network with docker desktop in M1 Chip

[wey-gu]

Please check the FAQ documentation before raising an issue

Describe the bug (required)

In Docker Desktop on macOS M1 chip(an ARM linux VM on macOS), it's found such issue is being reproduced 100%.

I had excluded other conditions:

• ARM64 VM on the cloud, confirmed this cannot be reproduced
• AMD64 VM in our lab, confirmed this cannot be reproduced

Your Environments (required)

• OS: uname -a
• Compiler: g++ --version or clang++ --version
• CPU: arm64 m1
• Commit id: 3.6.0

How To Reproduce(required)

Reproduce:

This can only be reproduced in my docker desktop, only when console was started from the docker network, if I am doing from outside of the container, it won't trigger this.

• create a space with :play basketballplayer from console
• create a tag with

CREATE TAG IF NOT EXISTS label_propagation (
    cluster_id string NOT NULL
);

• query from a console connected from a container with the same container network(nebula-net)

MATCH (v:player)
RETURN id(v) LIMIT 10;

Then it'll crash the Storaged:

F20230906 03:36:55.511937   292 Expression.cpp:526] Unknown expression: 1E 02 00 00 00 00 00 00 00 44(D) 23(#) 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 6C(l) 61(a) 62(b) 65(e) 6C(l) 5F(_) 70(p) 72(r) 6F(o) 70(p) 61(a) 67(g) 61(a) 74(t) 69(i) 6F(o) 6E(n) 04 00 00 00 00 00 00 00 5F(_) 74(t) 61(a) 67(g) 44(D) 23(#) 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 6C(l) 61(a) 62(b) 65(e) 6C(l) 5F(_) 70(p) 72(r) 6F(o) 70(p) 61(a) 67(g) 61(a) 74(t) 69(i) 6F(o) 6E(n) 04 00 00 00 00 00 00 00 5F(_) 74(t) 61(a) 67(g)
*** Check failure stack trace: ***
*** Aborted at 1693971415 (Unix time, try 'date -d @1693971415') ***
*** Signal 6 (SIGABRT) (0x1) received by PID 1 (pthread TID 0xffff54072810) (linux TID 292) (maybe from PID 1, UID 0) (code: -6), stack trace: ***
/usr/local/nebula/bin/nebula-storaged(_ZN5folly10symbolizer21SafeStackTracePrinter15printStackTraceEb+0x33)[0x2462373]
/usr/local/nebula/bin/nebula-storaged(_ZN5folly10symbolizer21SafeStackTracePrinter15printStackTraceEb+0x33)[0x2462373]
(safe mode, symbolizer not available)

---

Also here(https://discuss.nebula-graph.com.cn/t/topic/13878/5 ) it's reported(by @salahaz ) errors differentiated from different ways of connecting the network, but in the opposite result.

[wey-gu]

after cleaning up the spaces of basketballplayer and demo_basketballplayer, the issue cannot be reproduced, closing it first.