Changing Nixpacks Version

If you are using Nixpacks to build and deploy your application with Flightcontrol (Nixpacks is the default build type), you have the ability to specify the exact version of Nixpacks used to deploy each environment in your Flightcontrol project.

Flightcontrol chooses a Nixpacks version for you when you create a new environment in a Flightcontrol project (or a new Flightcontrol project). Typically, this Nixpacks version will be the latest, or close to the latest version - we monitor the Nixpacks releases for updates.

Generally speaking, this works well for everyone - for each environment, builds will be on the same version of Nixpacks, leading to a consistent process.

However, you may find that you need the latest version of Nixpacks, perhaps to pick up some underlying bug or enhancement. Here is a list of Nixpacks Releases, along with the associated changelogs.

Solution

Within the Flightcontrol dashboard or inside your flightcontrol.json file, specify an environment variable named NIXPACKS_VERSION with the value you want to specify. You can use any released version of Nixpacks with Flightcontrol.

Using the Dashboard

For instance, in the dashboard, add an environment variable:

NIXPACKS_VERSION=1.6.1

After adding the environment variable from the dashboard, you can Save and Deploy your project to trigger a new deployment with the Nixpacks version you specify.

Using flightcontrol.json

If you use flightcontrol.json for configuration, add an environment variable to your service:

{
    "environments": [
        {
            "id": "staging",
            "name": "Staging",
            ...
            "services": [
                {
                    "id": "staging-web-api",
                    "name": "Web API",
                    "type": "web",
                    "target": {"type": "fargate"},
                    "buildType": "nixpacks",
                    "ci": {
                        "type": "ec2"
                    },
                    "envVariables": {
                        "NIXPACKS_VERSION": "1.6.1",
                    }
                }
            ]
        }
    ]
}

Make a change to your flightcontrol.json file, and then merge that into your branch to trigger a deploy with the new changes.

If you’re having problems with your build, reach out to our Technical Support, and we’ll be happy to help you out.