Quarto check and render both failing while running in Docker

[SimonXIX]

I'm starting a Quarto project with Quarto 1.2.269 running in a Docker Ubuntu 22.04 container but no matter how I build the container the commands 'quarto check' and 'quarto render' both exit without completing and without displaying an error message like so:

root@8aa2102d5d93:/# quarto check

[✓] Checking Quarto installation......OK
      Version: 1.2.269
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

root@8aa2102d5d93:/# 

When I replicated the Docker container described in #2050, the build similarly failed on the Quarto command:

[+] Building 57.7s (8/9)                                                                             
 => [internal] load build definition from Dockerfile                                            0.0s
 => => transferring dockerfile: 407B                                                            0.0s
 => [internal] load .dockerignore                                                               0.0s
 => => transferring context: 2B                                                                 0.0s
 => [internal] load metadata for docker.io/library/nginx:latest                                 1.3s
 => [internal] load build context                                                               0.0s
 => => transferring context: 11.73kB                                                            0.0s
 => CACHED [build 1/4] FROM docker.io/library/nginx:latest@sha256:943c25b4b66b332184d5ba6bb182  0.0s
 => [build 2/4] COPY . /mysite                                                                  0.1s
 => [build 3/4] RUN apt-get update   && apt-get -y install wget ca-certificates   && wget "ht  37.5s
 => ERROR [build 4/4] RUN quarto check                                                         18.7s
------                                                                                               
 > [build 4/4] RUN quarto check:                                                                     
#0 4.270                                                                                             
[✓] Checking Quarto installation......OK                                                             
#0 4.274       Version: 1.2.269                                                                      
#0 4.274       Path: /opt/quarto/bin
#0 4.274 
[✓] Checking basic markdown render....OK
#0 18.32 
------
failed to solve: executor failed running [/bin/sh -c quarto check]: exit code: 1

For reference, my original Dockerfile is:

FROM amd64/ubuntu:22.04

RUN apt-get update && apt-get install -y --no-install-recommends \
    pip \
    ca-certificates \
    curl \
    gdebi-core \
    && rm -rf /var/lib/apt/lists/*

RUN curl -LO https://github.com/quarto-dev/quarto-cli/releases/download/v1.2.269/quarto-1.2.269-linux-amd64.deb
RUN gdebi --non-interactive quarto-1.2.269-linux-amd64.deb

COPY requirements.txt requirements.txt
RUN pip install -r requirements.txt

I'm really not sure why this is happening so any help would be much appreciated. Thanks.

[mcanouil]

The rocker project is building Ubuntu Docker images without troubles.
Check their setup (https://github.com/rocker-org/rocker-versioned2), in particular Quarto install script (https://github.com/rocker-org/rocker-versioned2/blob/master/scripts/install_quarto.sh).

PS: could you properly format your post using appropriate tags (backticks code chunk opened with ```{} closed with ```) not quote tag > ?

[SimonXIX]

Thanks, I'll have a look. After I posted this, I experimented with running my Docker setup on an Ubuntu server and it works as expected. It's only on my Mac where this issue occurs.

[eitsupi]

This is due to the amd64 emulation of Docker Desktop for arm64 mac.
It is not expected to occur on anything other than arm mac.

[SimonXIX]

Thanks, that's what I suspected from my testing on various different architectures.

[mcanouil]

Would specifying the platform when building the image solve this?

FROM --platform=linux/amd64 ...

(Not the only way to set the platform).

[SimonXIX]

No, I tried that.