Hi, trying to use buildpacks but no success.
flyctl deploy --app discoverbsd
==> Verifying app config
--> Verified app config
==> Building image
Remote builder fly-builder-polished-sun-6614 ready
==> Building image with Buildpacks
--> docker host: 20.10.12 linux x86_64
full: Pulling from paketobuildpacks/builder
Digest: sha256:f243ffe1395dfb8a26c62d555bb30402b58bd3e87e3cfdd04b0ac367140ee6a9
Status: Image is up to date for paketobuildpacks/builder:full
full-cnb: Pulling from paketobuildpacks/run
Digest: sha256:31691fdc9d8366884a037281276edff06acd2a52b6c7a89c837f7f484fb03abb
Status: Image is up to date for paketobuildpacks/run:full-cnb
===> DETECTING
10 of 18 buildpacks participating
paketo-buildpacks/ca-certificates 3.4.0
paketo-buildpacks/mri 0.8.5
paketo-buildpacks/bundler 0.5.5
paketo-buildpacks/bundle-install 0.5.4
paketo-buildpacks/node-engine 0.16.0
paketo-buildpacks/yarn 0.8.2
paketo-buildpacks/yarn-install 0.10.4
paketo-buildpacks/rails-assets 0.7.2
paketo-buildpacks/puma 0.4.2
paketo-buildpacks/node-module-bom 0.4.2
===> ANALYZING
Restoring metadata for "paketo-buildpacks/ca-certificates:helper" from app image
Restoring metadata for "paketo-buildpacks/mri:mri" from app image
Restoring metadata for "paketo-buildpacks/bundler:bundler" from app image
Restoring metadata for "paketo-buildpacks/bundle-install:launch-gems" from app image
Restoring metadata for "paketo-buildpacks/bundle-install:build-gems" from cache
Restoring metadata for "paketo-buildpacks/node-engine:node" from cache
Restoring metadata for "paketo-buildpacks/yarn:yarn" from cache
Restoring metadata for "paketo-buildpacks/yarn-install:build-modules" from cache
Restoring metadata for "paketo-buildpacks/rails-assets:assets" from app image
Restoring metadata for "paketo-buildpacks/node-module-bom:cyclonedx-node-module" from cache
===> RESTORING
Restoring data for "paketo-buildpacks/mri:mri" from cache
Restoring data for "paketo-buildpacks/bundler:bundler" from cache
Restoring data for "paketo-buildpacks/bundle-install:build-gems" from cache
Restoring data for "paketo-buildpacks/node-engine:node" from cache
Restoring data for "paketo-buildpacks/yarn:yarn" from cache
Restoring data for "paketo-buildpacks/yarn-install:build-modules" from cache
Restoring data for "paketo-buildpacks/node-module-bom:cyclonedx-node-module" from cache
===> BUILDING
Paketo Buildpack for CA Certificates 3.4.0
https://github.com/paketo-buildpacks/ca-certificates
Launch Helper: Reusing cached layer
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Paketo Buildpack for MRI 0.8.5
Resolving MRI version
Candidate version sources (in priority order):
Gemfile -> "3.1.2"
<unknown> -> ""
Selected MRI version (using Gemfile): 3.1.2
Reusing cached layer /layers/paketo-buildpacks_mri/mri
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Paketo Buildpack for Bundler 0.5.5
Resolving Bundler version
Candidate version sources (in priority order):
Gemfile.lock -> "2.*.*"
<unknown> -> ""
Selected Bundler version (using Gemfile.lock): 2.3.21
Reusing cached layer /layers/paketo-buildpacks_bundler/bundler
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Paketo Buildpack for Bundle Install 0.5.4
Reusing cached layer /layers/paketo-buildpacks_bundle-install/build-gems
Reusing cached layer /layers/paketo-buildpacks_bundle-install/launch-gems
Configuring build environment
BUNDLE_USER_CONFIG -> "/layers/paketo-buildpacks_bundle-install/build-gems/config"
Paketo Buildpack for Node Engine 0.16.0
Resolving Node Engine version
Candidate version sources (in priority order):
package.json -> "14.x"
<unknown> -> ""
Selected Node Engine version (using package.json): 14.20.0
Reusing cached layer /layers/paketo-buildpacks_node-engine/node
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Paketo Buildpack for Yarn 0.8.2
Reusing cached layer /layers/paketo-buildpacks_yarn/yarn
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Paketo Buildpack for Yarn Install 0.10.4
Resolving installation process
Process inputs:
yarn.lock -> Found
Reusing cached layer /layers/paketo-buildpacks_yarn-install/build-modules
Paketo Buildpack for Rails Assets 0.7.2
Reusing cached layer /layers/paketo-buildpacks_rails-assets/assets
Paketo Buildpack for Puma 0.4.2
Assigning launch processes:
web (default): bash -c bundle exec puma --bind tcp://0.0.0.0:${PORT:-9292}
Paketo Buildpack for Node Module Bill of Materials Generator 0.4.2
Resolving CycloneDX Node.js Module version
Selected CycloneDX Node.js Module version: 3.10.4
Reusing cached layer /layers/paketo-buildpacks_node-module-bom/cyclonedx-node-module
Configuring environment
Appending CycloneDX Node.js Module onto PATH
Running CycloneDX Node.js Module
Running 'cyclonedx-bom -o bom.json'
Completed in 3.626s
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to <layer>.sbom.<ext>, launch.sbom.<ext>, or build.sbom.<ext>.
===> EXPORTING
Reusing layer 'paketo-buildpacks/ca-certificates:helper'
Reusing layer 'paketo-buildpacks/mri:mri'
Reusing layer 'paketo-buildpacks/bundler:bundler'
Reusing layer 'paketo-buildpacks/bundle-install:launch-gems'
Reusing layer 'paketo-buildpacks/rails-assets:assets'
Adding 1/1 app layer(s)
Reusing layer 'launcher'
Reusing layer 'config'
Reusing layer 'process-types'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving registry.fly.io/discoverbsd:cache...
*** Images (8193c3e4c0c0):
registry.fly.io/discoverbsd:cache
registry.fly.io/discoverbsd:deployment-01GCGK77HG5SPD61R6CPKGZQ2K
Reusing cache layer 'paketo-buildpacks/mri:mri'
Reusing cache layer 'paketo-buildpacks/bundler:bundler'
Reusing cache layer 'paketo-buildpacks/bundle-install:build-gems'
Reusing cache layer 'paketo-buildpacks/node-engine:node'
Reusing cache layer 'paketo-buildpacks/yarn:yarn'
Reusing cache layer 'paketo-buildpacks/yarn-install:build-modules'
Reusing cache layer 'paketo-buildpacks/node-module-bom:cyclonedx-node-module'
--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/discoverbsd]
83d85471d9f8: Layer already exists
e16c9ae240be: Layer already exists
9497805c7bd5: Layer already exists
3063347dac4c: Pushed
8a8cda46f24c: Layer already exists
9311dbb73ce1: Layer already exists
539ac48dab94: Layer already exists
5648967d6ad4: Layer already exists
c23057e83cef: Layer already exists
74b3a22c1e0e: Layer already exists
c17ef1ce2f34: Layer already exists
d4d2c89abefe: Layer already exists
87a4a623e0dd: Layer already exists
4a641e21953d: Layer already exists
deployment-01GCGK77HG5SPD61R6CPKGZQ2K: digest: sha256:26c649a1ae1b474dc464b73786cc26b7346dc5eada107ea268533d2eedaa892d size: 3259
--> Pushing image done
image: registry.fly.io/discoverbsd:deployment-01GCGK77HG5SPD61R6CPKGZQ2K
image size: 994 MB
==> Creating release
--> release v5 created
--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: rails db:migrate
--> This release will not be available until the release command succeeds.
Starting instance
Configuring virtual machine
Pulling container image
Starting instance
Configuring virtual machine
Pulling container image
Starting instance
Configuring virtual machine
Pulling container image
Unpacking image
Unpacking image
Unpacking image
Starting instance
Configuring virtual machine
Pulling container image
Unpacking image
Preparing kernel init
Configuring firecracker
Starting virtual machine
Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
Preparing to run: `launcher rails db:migrate` as 1000
2022/09/09 07:53:17 listening on [fdaa:0:87f0:a7b:a992:db35:40e9:2]:22 (DNS: [fdaa::3]:53)
Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
Preparing to run: `launcher rails db:migrate` as 1000
2022/09/09 07:53:17 listening on [fdaa:0:87f0:a7b:a992:db35:40e9:2]:22 (DNS: [fdaa::3]:53)
Preparing kernel init
Configuring firecracker
Starting virtual machine
Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
Preparing to run: `launcher rails db:migrate` as 1000
2022/09/09 07:53:17 listening on [fdaa:0:87f0:a7b:a992:db35:40e9:2]:22 (DNS: [fdaa::3]:53)
Preparing kernel init
Configuring firecracker
Starting virtual machine
Setting up swapspace version 1, size = 512 MiB (536866816 bytes)
Preparing to run: `launcher rails db:migrate` as 1000
2022/09/09 07:53:17 listening on [fdaa:0:87f0:a7b:a992:db35:40e9:2]:22 (DNS: [fdaa::3]:53)
Starting clean up.
Starting clean up.
Starting clean up.
Starting clean up.
Error release command failed, deployment aborted
Here’s with LOG_LEVEL=debug
{
"data": {
"releaseCommandNode": {
"id": "rcmd_v6gwzp0mg8ey9ok7",
"instanceId": "45cae958",
"command": "rails db:migrate",
"status": "running",
"exitCode": null,
"inProgress": true,
"succeeded": false,
"failed": false
}
}
}
Running release task (running)... 🌏 DEBUG --> POST https://api.fly.io/graphql
{
"query": "query ($id: ID!) { releaseCommandNode: node(id: $id) { id ... on ReleaseCommand { id instanceId command status exitCode inProgress succeeded failed } } }",
"variables": {
"id": "rcmd_v6gwzp0mg8ey9ok7"
}
}
DEBUG {}
DEBUG <-- 200 https://api.fly.io/graphql (109.89ms)
{
"data": {
"releaseCommandNode": {
"id": "rcmd_v6gwzp0mg8ey9ok7",
"instanceId": "45cae958",
"command": "rails db:migrate",
"status": "failed",
"exitCode": null,
"inProgress": false,
"succeeded": false,
"failed": true
}
}
}
Error release command failed, deployment aborted
Here’s my config:
# fly.toml file generated for discoverbsd on 2022-08-26T06:55:05-04:00
app = "discoverbsd"
kill_signal = "SIGINT"
kill_timeout = 5
[build]
builder = "paketobuildpacks/builder:full"
buildpacks = ["paketo-buildpacks/ruby", "paketo-buildpacks/nodejs"]
[build.args]
SECRET_KEY_BASE="asdf"
[deploy]
release_command = "rails db:migrate"
[env]
[experimental]
allowed_public_ports = []
auto_rollback = true
cmd = []
entrypoint = []
exec = []
[processes]
app = "puma -C config/puma.rb"
webpacker = "bin/webpack"
worker = "rails jobs:work"
[[services]]
http_checks = []
internal_port = 8080
processes = ["app"]
protocol = "tcp"
script_checks = []
[services.concurrency]
hard_limit = 25
soft_limit = 20
type = "connections"
[[services.ports]]
force_https = true
handlers = ["http"]
port = 80
[[services.ports]]
handlers = ["tls", "http"]
port = 443
[[services.tcp_checks]]
grace_period = "1s"
interval = "15s"
restart_limit = 0
timeout = "2s"
Can I somehow get info on what went wrong?