An unknown error occurred re postgres

It appears the most recent failure was a deploy issue? An unknown error occurred re postgres - #17 by cinjon

You’ll need to rerun that with LOG_LEVEL=debug fly deploy to diagnose that error message.

I switched over to using v320 everywhere instead of v259, added in the LOG_LEVEL=‘debug’, and got the following:

docker run -i --rm -v /path:/path:ro -v /var/run/docker.sock:/var/run/docker.sock -v /path/.fly:/.fly -w /path --network host --env FLY_NO_UPDATE_CHECK=1 --env FLY_API_TOKEN --env BUILDKIT_PROGRESS=plain --env LOG_LEVEL=debug flyio/flyctl:v0.0.320 -c /path/fly/fly.ipfs.toml deploy --detach --local-only --build-target deploy --dockerfile docker/Dockerfile.ipfs
...
DEBUG Failed storing buildDEBUG Trying 'Buildpacks' strategy
DEBUG no buildpack builder configured, skipping
DEBUG result image:<nil> error:<nil>
DEBUG Trying 'Dockerfile' strategy
==> Creating build context
--> Creating build context done
DEBUG fetching docker server info
==> Building image with Docker
--> docker host: 20.10.13 linux x86_64
DEBUG buildkitEnabled%!!(MISSING)(EXTRA bool=true)#1 [internal] load remote build context
Sending build context to Docker daemon  116.4MB
#1 DONE 27.1s

#1 [internal] load remote build context
#1 DONE 0.0s

#2 copy /context /
#2 DONE 4.8s

#3 [internal] load metadata for docker.io/ipfs/go-ipfs:v0.11.0-rc1
#3 DONE 1.2s

#5 [1/2] FROM docker.io/ipfs/go-ipfs:v0.11.0-rc1@sha256:705fee004ad9c2f7573551f4eb16e10b01bcd3b81f971820c1aa2bd96e1fee8c
#5 DONE 0.0s

#4 [2/2] COPY packages/ipfs/bin/container_daemon /usr/local/bin/start_ipfs
#4 CACHED

#6 exporting to image
#6 exporting layers done
#6 writing image sha256:7d645de8a1e9635c9d2c96f385e2b2a4659564facd104e416e7d2e97a94eb0cd
#6 writing image sha256:7d645de8a1e9635c9d2c96f385e2b2a4659564facd104e416e7d2e97a94eb0cd done
#6 naming to registry.fly.io/rpt-rinkeby-320-ipfs:deployment-1650310289 done
#6 DONE 0.0s
DEBUG result image:<nil> error:error building: open build.log: read-only file system
Error failed to fetch an image or build from source: error building: open build.log: read-only file system

@kurt, do you have guidance on the above? I’m going kind of crazy right now trying to get this working. It seems like the team is suggesting that we have to use a recent version in order to operate postgres, but when i do that, i get this other error above that isn’t of much help in narrowing where to look. I’m a bit surprised that no one else is running into this…

If I try running this without the “:ro” on the “…-v /path:/path:ro -v …”, I get a different error:

DEBUG result image:&{ID:sha256:7d645de8a1e9635c9d2c96f385e2b2a4659564facd104e416e7d2e97a94eb0cd Tag:registry.fly.io/rpt-rinkeby-320-ipfs:deployment-1650311992 Size:83012542} error:<nil>
image: registry.fly.io/rpt-rinkeby-320-ipfs:deployment-1650311992
image size: 83 MB
==> Creating release
DEBUG --> POST https://api.fly.io/graphql {{"query":"mutation($input: DeployImageInput!) { deployImage(input: $input) { release { id version reason description deploymentStrategy user { id email name } evaluationId createdAt } releaseCommand { id command evaluationId } } }","variables":{"input":{"appId":"rpt-rinkeby-320-ipfs","image":"registry.fly.io/rpt-rinkeby-320-ipfs:deployment-1650311992","services":null,"definition":{"env":{"IPFS_PROFILE":"server","PORT":"8080"},"experimental":{"allowed_public_ports":[],"auto_rollback":true,"private_network":true},"kill_signal":"SIGINT","kill_timeout":5,"mounts":[{"destination":"/data/ipfs","source":"researchportfolio_data_ipfs_0"}],"processes":["app"],"services":[{"concurrency":{"hard_limit":25,"soft_limit":20,"type":"connections"},"http_checks":[],"internal_port":8080,"ports":[{"handlers":["http"],"port":80},{"handlers":["tls","http"],"port":443}],"processes":["app"],"protocol":"tcp","script_checks":[]}]},"strategy":null}}}
}
DEBUG <-- 500 https://api.fly.io/graphql (2.33s) {"errors":[{"message":"An unknown error occured.","extensions":{"code":"SERVER_ERROR"}}],"data":{}}
Error An unknown error occured.