balzack
Workflow to publish container image to GHCR
I've been publishing the databag container to GHCR from my fork in order to make updating my deployment more automated. This allows me to do a simple docker compose pull && docker compose up whenever a new release occurs. This is a common deployment method for folks interested in self-hosting services and would make it easier for new folks using databag.
@balzack would you be interested in having this behavior here in the main repo as well? I can also write up instructions on setting up a deployment with docker compose.
@mbaum0 if it helps people use the service, I am all for it. If you don't mind writing up the instructions, please do so. Thank you!
I've got the new workflow in place but ran into a yarn when trying to build the linux/arm64 container image
> [linux/amd64 node 4/6] RUN --mount=type=cache,target=/root/.yarn YARN_CACHE_FOLDER=/root/.yarn yarn --frozen-lockfile:
53.84 warning "react-scripts > eslint-config-react-app > [email protected]" has unmet peer dependency "@babel/plugin-syntax-flow@^7.14.5".
53.84 warning "react-scripts > eslint-config-react-app > [email protected]" has unmet peer dependency "@babel/plugin-transform-react-jsx@^7.14.9".
53.86 warning "react-scripts > react-dev-utils > [email protected]" has unmet peer dependency "typescript@>= 2.7".
53.87 warning "babel-jest > babel-preset-jest > [email protected]" has unmet peer dependency "@babel/core@^7.0.0".
53.88 warning "react-scripts > eslint-config-react-app > @typescript-eslint/eslint-plugin > [email protected]" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
53.89 warning " > [email protected]" has unmet peer dependency "react-is@>= 16.8.0".
53.89 warning " > [email protected]" has unmet peer dependency "@babel/core@^7.8.0".
53.89 warning "babel-jest > [email protected]" has unmet peer dependency "@babel/core@^7.0.0".
54.48 error Error: ENOENT: no such file or directory, open '/root/.yarn/v6/npm-@ant-design-icons-5.3.7-d9f3654bf7934ee5faba43f91b5a187f5309ec68-integrity/node_modules/@ant-design/icons/.yarn-metadata.json'
54.48 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
I am not sure if this helps, but when I build the multiarch container image in buildx, I pass the platform switch as:
--platform linux/arm64/v8,linux/amd64