What happened
When trying to deploy with docker & portainer, I get the following warning & error:
WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-tree
failed to solve: process "/bin/sh -c npm ci --omit=dev && npm cache clean --force" did not complete successfully: exit code: 127
Running docker compose build --no-cache feedzero 2>&1 | tail -50, I get the same error.
When trying to pull the docker image directly, I get the following error, suggesting it's either private, restricted or doesn't exist:
Error response from daemon: pull access denied for forcingfx/feedzero, repository does not exist or may require 'docker login'
I get a similar error pulling the ghcr image directly:
Error response from daemon: error from registry: denied
I've spent a few hours trying to manually create a local image, editing the package.json, Dockerfile & docker-compose.yml files, trying to fix the first error (which I can't remember how I did anymore), and then having to delete a directory named "Caddyfile" & replacing it with a file named "Caddyfile", because something (I can't remember anymore) was initially expecting a file but got a directory instead. I was jumping through to many hoops to list here, and I still couldn't get it working. The closest I got was Portainer reporting all containers as running & healthy, yet when I visited the IPv4 address, I got the following error & just gave up afterwards:
SSL_ERROR_RX_RECORD_TOO_LONG
Very frustrating, mostly because I couldn't figure this out.
Expected behavior
I expected it to just work after following the documentation for deploying this with docker & portainer. I should be able to just copy/paste contents of .yml & .env files into a stack, set a name for the stack, click "Deploy the stack" in portainer & be done.
Steps to reproduce
- ran
git clone https://github.com/forcingfx/feedzero.git
- ran
cd feedzero
- ran
cp .env.example .env
- ran
nano .env
- entered the following:
"HOSTNAME=[insert my IPv4 here]
ACME_EMAIL=
FEEDZERO_VERSION=latest
DATA_DIR=./data", and saved it.
- ran
./scripts/feedzero doctor, everything reported good
- ran
./scripts/feedzero up, got the first error as described at the start of this report
Browser + version
No response
Reader version
No response
Additional context
No response
What happened
When trying to deploy with docker & portainer, I get the following warning & error:
WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-treefailed to solve: process "/bin/sh -c npm ci --omit=dev && npm cache clean --force" did not complete successfully: exit code: 127Running
docker compose build --no-cache feedzero 2>&1 | tail -50, I get the same error.When trying to pull the docker image directly, I get the following error, suggesting it's either private, restricted or doesn't exist:
Error response from daemon: pull access denied for forcingfx/feedzero, repository does not exist or may require 'docker login'I get a similar error pulling the ghcr image directly:
Error response from daemon: error from registry: deniedI've spent a few hours trying to manually create a local image, editing the package.json, Dockerfile & docker-compose.yml files, trying to fix the first error (which I can't remember how I did anymore), and then having to delete a directory named "Caddyfile" & replacing it with a file named "Caddyfile", because something (I can't remember anymore) was initially expecting a file but got a directory instead. I was jumping through to many hoops to list here, and I still couldn't get it working. The closest I got was Portainer reporting all containers as running & healthy, yet when I visited the IPv4 address, I got the following error & just gave up afterwards:
SSL_ERROR_RX_RECORD_TOO_LONGVery frustrating, mostly because I couldn't figure this out.
Expected behavior
I expected it to just work after following the documentation for deploying this with docker & portainer. I should be able to just copy/paste contents of
.yml&.envfiles into a stack, set a name for the stack, click "Deploy the stack" in portainer & be done.Steps to reproduce
git clone https://github.com/forcingfx/feedzero.gitcd feedzerocp .env.example .envnano .env"HOSTNAME=[insert my IPv4 here]
ACME_EMAIL=
FEEDZERO_VERSION=latest
DATA_DIR=./data", and saved it.
./scripts/feedzero doctor, everything reported good./scripts/feedzero up, got the first error as described at the start of this reportBrowser + version
No response
Reader version
No response
Additional context
No response