-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDDS-11631. Add Run with Docker Compose guide #101
base: HDDS-9225-website-v2
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
--- | ||
sidebar_label: Docker | ||
--- | ||
|
||
# Troubleshooting Ozone in Docker | ||
|
||
**TODO:** File a subtask under [HDDS-9860](https://issues.apache.org/jira/browse/HDDS-9860) and complete this page or section. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"packageManager": "pnpm@8.7.1", | ||
"packageManager": "pnpm@9.12.3", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you clarify why we need the pnpm version bump? Is mermaid incompatible with older versions? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. With 0.280 ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-8.7.1.tgz
1.109 ERR_PNPM_LOCKFILE_BREAKING_CHANGE Lockfile /ozone-site/pnpm-lock.yaml not compatible with current pnpm
1.109
1.109 Run with the --force parameter to recreate the lockfile.
------
failed to solve: process "/bin/sh -c pnpm install --prod --frozen-lockfile" did not complete successfully: exit code: 1
`docker-compose` process finished with exit code 17 I added the docusaurus/theme-mermaid package via |
||
"name": "doc-site", | ||
"version": "0.1.0", | ||
"private": true, | ||
|
@@ -16,22 +16,23 @@ | |
}, | ||
"dependencies": { | ||
"@docusaurus/core": "3.3.2", | ||
"@docusaurus/preset-classic": "3.3.2", | ||
"@docusaurus/plugin-pwa": "3.3.2", | ||
"@docusaurus/preset-classic": "3.3.2", | ||
"@docusaurus/theme-mermaid": "3.3.2", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I checked out this change and ran
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I saw that I faced the same problem after uninstalling docusaurus/theme-mermaid. |
||
"@mdx-js/react": "^3.0.0", | ||
"ajv": "^8.12.0", | ||
"clsx": "^2.1.0", | ||
"prism-react-renderer": "^2.3.1", | ||
"react": "^18.2.0", | ||
"react-dom": "^18.2.0", | ||
"ajv": "^8.12.0" | ||
"react-dom": "^18.2.0" | ||
}, | ||
"devDependencies": { | ||
"@docusaurus/module-type-aliases": "3.3.2", | ||
"cspell": "^8.2.1", | ||
"@cspell/dict-docker": "^1.1.7", | ||
"@cspell/dict-java": "^5.0.6", | ||
"@cspell/dict-markdown": "^2.0.1", | ||
"@cspell/dict-shell": "^1.0.6", | ||
"@docusaurus/module-type-aliases": "3.3.2", | ||
"cspell": "^8.2.1", | ||
"markdownlint-cli": "^0.39.0" | ||
}, | ||
"browserslist": { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can delete the TODO above this section since we are filling in the page in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed