metabase / metabase/metabase

Building Metabase on a containerized environment does not work straight away

Open
#58,322 3 comments 1 reaction 0 assignees View on GitHub
.Needs Triage Type:Bug
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

The command defined in the docs section [Build a Metabase Uberjar in a containerized environment](https://www.metabase.com/docs/latest/developers-guide/build#build-a-metabase-uberjar-in-a-containerized-environment) does not work:

https://github.com/metabase/metabase/blob/e8faba9fe89f5f6275a3b72be7f3896f704ec8ae/docs/developers-guide/build.md?plain=1#L164-L172

When running the above command, I get the following error message:

```
Dockerfile:29
--------------------
27 | RUN yarn --frozen-lockfile
28 |
29 | >>> RUN INTERACTIVE=false CI=true MB_EDITION=$MB_EDITION bin/build.sh :version ${VERSION}
30 |
31 | # ###################
--------------------
ERROR: failed to solve: process "/bin/sh -c INTERACTIVE=false CI=true MB_EDITION=$MB_EDITION bin/build.sh :version ${VERSION}" did not complete successfully: exit code: 1
```

Adding a specific version as an argument solved solved the issue:
```bash
DOCKER_BUILDKIT=1 docker build --build-arg VERSION=v1.54.9 --output container-output/ .
```

Maybe that should be reflected in the docs.

Contributor guide

Open the contributing guide

Research direction

Open docs/developers-guide/build.md around lines 164-172 and review the containerized Uberjar build command. Reproduce the reported command, then update the documentation to reflect the VERSION argument that makes the build work and rerun the container build to confirm the documented command succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure, docker
Domain
build-system, devops, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.