You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because enmotech/opengauss cannot be used in WSL environment.
2024-12-14 15:19:34.355 [unknown] [unknown] localhost 140448798433216 0[0:0#0] 0 [BACKEND] LOG: user configure file is not found, it will be created.
2024-12-14 15:19:34.360 [unknown] [unknown] localhost 140448798433216 0[0:0#0] 0 [BACKEND] LOG: the configure file /usr/local/opengauss/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user!2024-12-14 15:19:34.360 [unknown] [unknown] localhost 140448798433216 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file.[2024-12-14 15:19:39.965][179][][gs_ctl]: gaussDB state is Coredump[2024-12-14 15:19:39.965][179][][gs_ctl]: stopped waiting[2024-12-14 15:19:39.965][179][][gs_ctl]: could not start serverExamine the log output.
enmotech/opengauss-lite
. Check https://hub.docker.com/r/enmotech/opengauss-lite . This also involves the follow-up impact ofB
模式创建数据库后连接报错 #39 and Add DBCOMPATIBILITY 'B' parameter to opengauss database apache/shardingsphere#34062 .enmotech/opengauss
cannot be used in WSL environment.enmotech/opengauss-lite
need the--privileged=true
flag? It's not common to use privileged Docker containers in scenarios such as testcontainers-java when writing unit tests. It seems that the README does not mention it. An early investigation came from Improve GraalVM Reachability Metadata and corresponding nativeTest related unit tests apache/shardingsphere#29052 .The text was updated successfully, but these errors were encountered: