【问题标题】:Failed to launch Base! /app/.local-chromium/Linux-706915/chrome-linux/chrome: ... libX11.so.6启动基地失败! /app/.local-chromium/Linux-706915/chrome-linux/chrome: ... libX11.so.6
【发布时间】:2020-10-10 11:32:22
【问题描述】:

我有一个在 ASP.NET Core 3.1 上运行的 puppeteer-sharp 实例,它在本地运行良好。对于部署,它构建在 docker 容器中并部署到 K8 开发集群。 docker 容器构建良好,但应用程序在运行时失败,并在尝试使用 puppeteer-sharp 时出现错误 Failed to launch Base! /app/.local-chromium/Linux-706915/chrome-linux/chrome: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory

从以下资源中,我拼凑了以下 dockerfile。我对 docker 还很陌生,所以想象一下配置有问题,但我愿意接受建议!

使用的资源:

Dockerfile:

#See https://aka.ms/containerfastmode to understand how Visual Studio uses this Dockerfile to build your images for faster debugging.

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443


FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster AS build
WORKDIR /src

#####################
#PUPPETEER RECIPE
#####################
# Install latest chrome dev package and fonts to support major charsets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)
# Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer
# installs, work.
ARG CHROME_VERSION="81.0.4044.138-1"
RUN apt-get update && apt-get -f install && apt-get -y install apt-utils wget gnupg2 
RUN apt-get -f install && apt-get -y install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils
RUN wget --no-verbose -O /tmp/chrome.deb http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${CHROME_VERSION}_amd64.deb \
&& apt-get update \
&& apt-get install -y /tmp/chrome.deb --no-install-recommends --allow-downgrades \
&& rm /tmp/chrome.deb

# NOTE: REMOVED THIS WHILST DEBUGGING - D
# Add user, so we don't need --no-sandbox.
# same layer as npm install to keep re-chowned files from using up several hundred MBs more space    
#RUN groupadd -r pptruser && useradd -r -g pptruser -G audio,video pptruser \
    #&& mkdir -p /home/pptruser/Downloads \
    #&& chown -R pptruser:pptruser /home/pptruser
#
## Run everything after as non-privileged user.
#
#USER pptruser

ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/google-chrome-unstable"

#####################
#END PUPPETEER RECIPE
#####################


COPY ["ProjectName.Core/ProjectName.Core.csproj", "ProjectName.Core/"]
RUN dotnet restore "ProjectName.Core/ProjectName.Core.csproj"
COPY . .
WORKDIR "/src/ProjectName.Core"
RUN dotnet build "ProjectName.Core.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "ProjectName.Core.csproj" -c Release -o /app/publish

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "ProjectName.Core.dll"]

代码实现:

        public static async Task<Stream> GeneratePdfFromHtml(string html, List<string> styleUrls = null)
        {
            await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);

            var browser = await Puppeteer.LaunchAsync(new LaunchOptions
            {
                Headless = true                
            });

            using (var page = await browser.NewPageAsync())
            {
                await page.SetContentAsync(html);

                if(styleUrls != null)
                    foreach (var url in styleUrls)
                    {
                        await page.AddStyleTagAsync(url);
                    }

                return await page.PdfStreamAsync();                
            }
        }

使用 Docker 的资源都针对 .NET Core 2.0,所以我不知道这是否与它有关。它在 Docker 环境之外运行良好的事实表明 .NET Core 版本不是问题,更有可能是 dockerfile 本身的一个步骤。

【问题讨论】:

    标签: c# docker asp.net-core-3.1 puppeteer-sharp


    【解决方案1】:

    好吧,事实证明这是混合的。 dockerfile 需要重新排列,并且在没有沙箱的情况下效果最好。如您所见,原始代码是在中间映像上安装依赖项,而不是在 final/base 上。

    由于某种原因,我无法让它在沙盒用户下正常工作,因此已将其删除。因此,需要更新实现以启用 --no-sandbox 参数。

    这里是其他任何努力让 puppeteer-sharp 使用 .NET Core 3.1 的人的更新代码。

    dockerfile

    #See https://aka.ms/containerfastmode to understand how Visual Studio uses this Dockerfile to build your images for faster debugging.
    
    FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base
    #####################
    #PUPPETEER RECIPE
    #####################
    # Install latest chrome dev package and fonts to support major charsets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)
    # Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer
    # installs, work.
    ARG CHROME_VERSION="81.0.4044.138-1"
    RUN apt-get update && apt-get -f install && apt-get -y install wget gnupg2 apt-utils
    RUN wget --no-verbose -O /tmp/chrome.deb http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${CHROME_VERSION}_amd64.deb \
    && apt-get update \
    && apt-get install -y /tmp/chrome.deb --no-install-recommends --allow-downgrades fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf \
    && rm /tmp/chrome.deb
    
    ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/google-chrome"
    #####################
    #END PUPPETEER RECIPE
    #####################
    
    WORKDIR /app
    EXPOSE 80
    EXPOSE 443
    
    
    FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster AS build
    WORKDIR /src
    
    
    COPY ["ProjectName.Core/ProjectName.Core.csproj", "ProjectName.Core/"]
    RUN dotnet restore "ProjectName.Core/ProjectName.Core.csproj"
    
    
    COPY . .
    WORKDIR "/src/ProjectName.Core"
    RUN dotnet build "ProjectName.Core.csproj" -c Release -o /app/build
    
    FROM build AS publish
    RUN dotnet publish "ProjectName.Core.csproj" -c Release -o /app/publish
    
    FROM base AS final
    WORKDIR /app
    COPY --from=publish /app/publish .
    ENTRYPOINT ["dotnet", "ProjectName.Core.dll"]
    

    实施

    public static async Task<Stream> GeneratePdfFromHtml(string html, List<string> styleUrls = null)
    {
        await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);
    
        var browser = await Puppeteer.LaunchAsync(new LaunchOptions
        {
            Args = new[] { "--no-sandbox" },
            Headless = true                
        });
    
        using (var page = await browser.NewPageAsync())
        {
            await page.SetContentAsync(html);
    
            if(styleUrls != null)
                foreach (var url in styleUrls)
                {
                    await page.AddStyleTagAsync(new AddTagOptions { Path = url });
                }
    
            return await page.PdfStreamAsync();                
        }
    }
    

    可能值得注意的是,puppeteer-sharp 的 docker 实现似乎也存在使用本地 url 查找样式表的问题(例如 localhost:1234/lib/bootsrap/bootsrap.min.css)。它只是永远挂起和旋转,因此将 AddStyleTagAsync() 更改为使用文件路径。别忘了,它位于 IHostingEnvironment.WebRootPath 下,为您节省了 google 搜索。

    希望这对其他人有所帮助。毫无疑问,在不远的将来,它也会再次穿越我的道路!

    【讨论】:

    • 我运行了你的 Dockfile,它给了我这个错误:1&gt;failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c apt-get update &amp;&amp; apt-get -f install &amp;&amp; apt-get -y install wget gnupg2 apt-utils]: runc did not terminate sucessfully 如果我在“FROM mcr.microsoft.com/dotnet/core/”之后移动 PUPPETEER RECIPE,它不会给我这个错误sdk:3.1-buster AS build”,但随后它给出了与您的问题完全相同的错误。你有什么主意吗?谢谢。
    猜你喜欢
    • 1970-01-01
    • 2013-10-02
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2014-12-12
    • 2023-04-08
    相关资源
    最近更新 更多