admin 管理员组

文章数量: 1086019

I run this code as part of my aws lambda with docker image:

import plotly.io as pio
import base64
import io
import plotly.graph_objects as go

def fig_to_base64(fig: go.Figure):
    buffer = io.BytesIO()

    if "--single-process" not in pio.kaleido.scope.chromium_args:
        pio.kaleido.scope.chromium_args += ("--single-process",)

    pio.write_image(fig=fig, file=buffer, format="png", engine="kaleido")
    buffer.seek(0)
    plot_base64 = base64.b64encode(buffer.read()).decode("utf-8")
    buffer.close()

    return plot_base64

The issue that I get 30% of the time is the following error crash (there are times which it work fine!):

Failed to start Kaleido subprocess. Error stream:
[0327/100250.883361:WARNING:resource_bundle(431)] locale_file_path.empty() for locale 
prctl(PR_SET_NO_NEW_PRIVS) failed
prctl(PR_SET_NO_NEW_PRIVS) failed
[0327/100251.087148:FATAL:zygote_communication_linux(255)] Cannot communicate with zygote
#0 0x55555555555 base::debug::CollectStackTrace()
#1 0x55555555555 base::debug::StackTrace::StackTrace()
#2 0x55555555555 logging::LogMessage::~LogMessage()
#3 0x55555555555 content::ZygoteCommunication::Init()
#4 0x55555555555 content::CreateGenericZygote()
#5 0x55555555555 content::ContentMainRunnerImpl::Initialize()
#6 0x55555555555 content::RunContentProcess()
#7 0x55555555555 content::ContentMain()
#8 0x55555555555 headless::(anonymous namespace)::RunContentMain()
#9 0x55555555555 headless::HeadlessBrowserMain()
#10 0x55555555555 main
#11 0x55555555555 __libc_start_call_main
#12 0x55555555555 __libc_start_main_alias_2
#13 0x55555555555 _start
Received signal 6
#0 0x55555555555 base::debug::CollectStackTrace()
#1 0x55555555555 base::debug::StackTrace::StackTrace()
#2 0x55555555555 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x55555555555 (/usr/lib64/libc.so.6+0x54ddf)
#4 0x55555555555 __pthread_kill_implementation
#5 0x55555555555 __GI_raise
#6 0x55555555555 __GI_abort
#7 0x55555555555 base::debug::BreakDebugger()
#8 0x55555555555 logging::LogMessage::~LogMessage()
#9 0x55555555555 content::ZygoteCommunication::Init()
#10 0x55555555555 content::CreateGenericZygote()
#11 0x55555555555 content::ContentMainRunnerImpl::Initialize()
#12 0x55555555555 content::RunContentProcess()
#13 0x55555555555 content::ContentMain()
#14 0x55555555555 headless::(anonymous namespace)::RunContentMain()
#15 0x55555555555 headless::HeadlessBrowserMain()
#16 0x55555555555 main
#17 0x55555555555 __libc_start_call_main
#18 0x55555555555 __libc_start_main_alias_2
#19 0x55555555555 _start
r8: 0x55555555555  r9: 0x55555555555 r10: 0x55555555555 r11: 0x55555555555
r12: 0x55555555555 r13: 0x55555555555 r14: 00007ffd6fd6d1b0 r15: 0x55555555555
di: 0x55555555555  si: 0x55555555555  bp: 0x55555555555  bx: 0x55555555555
dx: 0x55555555555  ax: 0x55555555555  cx: 0x55555555555  sp: 0x55555555555
ip: 0x55555555555 efl: 0x55555555555 cgf: 0x55555555555 erf: 0x55555555555
trp: 0x55555555555 msk: 0x55555555555 cr2: 0x55555555555
[end of stack trace]
Calling _exit(1). Core file will not be generated.

(I changed all the values with 0x55555555555)

I tried as u can see above to use the flag of --singe_process, so it will run on single_process but it is not helps (Also kaleido should automatically identify that we run on aws lambda env, but yet I made sure to insert the flag manually in case it won't identify the aws lambda env)

本文标签： Kaleido fails on AWS Lambda with dockerStack Overflow

版权声明：本文标题：Kaleido fails on AWS Lambda with docker - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://roclinux.cn/p/1744085226a2530997.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。