ActivityPub container not starting

I’m running the activitypub setup as a server on a separate service from my ghost server instances which handles the activitypub requests for all of my ghost instances. I’m running it from the github repo with a few of the testing containers removed. I’m getting the following with anything after the github tag 1.2.7 and this service does not start so the nginx service is posting no route to host

activitypub-1  | ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-12.11.0.tgz
activitypub-1  | Downloading the pnpm 12.11.0 binary for linux-x64...
activitypub-1  | Update available! 12.11.0 → 12.11.2.
activitypub-1  | Changelog: https://pnpm.io/v/12.11.2
activitypub-1  | To update, run: curl -fsSL https://get.pnpm.io/install.sh | sh -
activitypub-1  | Added 12 entries to minimumReleaseAgeExclude in pnpm-workspace.yaml (set minimumReleaseAgeStrict to true to gate these updates with a prompt):
activitypub-1  |   @fedify/cli@2.4.4
activitypub-1  |   @fedify/fedify@2.4.4
activitypub-1  |   @fedify/hono@2.4.4
activitypub-1  |   @fedify/init@2.4.4
activitypub-1  |   @fedify/redis@2.4.4
activitypub-1  |   @fedify/relay@2.4.4
activitypub-1  |   @fedify/sqlite@2.4.4
activitypub-1  |   @fedify/uri-template@2.4.4
activitypub-1  |   @fedify/vocab-runtime@2.4.4
activitypub-1  |   @fedify/vocab-tools@2.4.4
activitypub-1  |   @fedify/vocab@2.4.4
activitypub-1  |   @fedify/webfinger@2.4.4
activitypub-1  | [WARN] 2 deprecated subdependencies found: node-domexception@1.0.0, tsconfck@3.1.6
activitypub-1  | Packages: -43
activitypub-1  | -------------------------------------------
activitypub-1  | Agent skills awaiting approval: @fedify/fedify, @logtape/logtape.
activitypub-1  | Run "pnpm approve" to review them.
activitypub-1  | [WARN] Issues with peer dependencies found. Run "pnpm peers check" to list them.
activitypub-1  | Error: ERR_PNPM_IGNORED_BUILDS
activitypub-1  |
activitypub-1  |   × installing dependencies
activitypub-1  |   ╰─▶ Ignored build scripts: protobufjs@7.6.6
activitypub-1  |   help: Run "pnpm approve-builds" to pick which dependencies should be allowed
activitypub-1  |         to run scripts.
activitypub-1  |
activitypub-1  | [WARN] The install that runs before scripts failed, so your node_modules may be out of sync with your lockfile. Set "verifyDepsBeforeRun: false" to skip this install.
activitypub-1  | $ concurrently "pnpm build:dev --watch" "node --inspect=0.0.0.0:9229 --watch dist/app.js"
activitypub-1  | sh: concurrently: not found
activitypub-1  | [ELIFECYCLE] Command failed with exit code 127.
activitypub-1  | ? Verifying lockfile against supply-chain policies (786 entries)...
activitypub-1  | ✓ Lockfile passes supply-chain policies (786 entries in 1.2s)
activitypub-1  | Lockfile is up to date, resolution step is skipped
activitypub-1  | Already up to date
activitypub-1  | Agent skills awaiting approval: @fedify/fedify, @logtape/logtape.
activitypub-1  | Run "pnpm approve" to review them.
activitypub-1  | Error: ERR_PNPM_IGNORED_BUILDS
activitypub-1  |
activitypub-1  |   × installing dependencies
activitypub-1  |   ╰─▶ Ignored build scripts: protobufjs@7.6.6
activitypub-1  |   help: Run "pnpm approve-builds" to pick which dependencies should be allowed
activitypub-1  |         to run scripts.
activitypub-1  |
activitypub-1  | [WARN] The install that runs before scripts failed, so your node_modules may be out of sync with your lockfile. Set "verifyDepsBeforeRun: false" to skip this install.
activitypub-1  | $ concurrently "pnpm build:dev --watch" "node --inspect=0.0.0.0:9229 --watch dist/app.js"
activitypub-1  | sh: concurrently: not found
activitypub-1  | [ELIFECYCLE] Command failed with exit code 127.

im not exactly following the directions on the github readme. i made my own docker-compose based on the project’s and stripping out the testing containers, so i only have the following services in my compose file - activitypub, migrate, nginx, pubsub, and fake-gcs. i am then starting the stack with

docker compose up activitypub nginx -d --build

this has worked for me for quite a while. im not sure what im missing here, it looks like there was a change to move to pnpm at some point which i think is what im having a problem with and not sure how to fix this.

im not exactly following the directions on the github readme. i made my own docker-compose based on the project’s and stripping out the testing containers

The docker-compose file in the ActivityPub repo is intended for local development on the source code itself. Most likely, you’ll want to customize/borrow pieces from the ghost-docker setup. The compose setup in that repo uses the versioned, ghcr-published ActivityPub images and is likely to be a lot more stable than running the development setup from the ActivityPub repo.

Thanks I did compare the compose services and updated them. The missing concurrently is what I’ve been trying to figure out. the comments in the pnpm-workspace indicate it should be building without them since it should be using the --ignore-scripts. im going to keep digging into this part of it.

@acburdine are you saying that container, if run on a separate box, can respond to multitenant ap requests? that might make it easier but i didnt think thats how that container worked. im directing requests to this single server for all of my ghost instances using this in my nginx proxy

        location ~ /.ghost/activitypub/* {
        proxy_set_header        Host              $host;
        proxy_set_header        Authorization     $http_authorization;
        proxy_set_header        X-Real-IP         $remote_addr;
        proxy_set_header        X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header        X-Forwarded-Proto $scheme;
        proxy_no_cache          1;
        proxy_cache_bypass      1;
        proxy_ssl_server_name on;
        set $upstream_app activitypubServerName
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }

im doing this because i dont want to have a whole instance of all of this for each instance of ghost.

are you saying that container, if run on a separate box, can respond to multitenant ap requests?

Yup - the container the ghost-docker setup uses is the production container published for versioned tags on the ActivityPub repo (Package activitypub · GitHub). So using that container you’re saving yourself the unnecessarily dependency installation and build step :sweat_smile:

My guess is you’re running into various issues because the development compose setup is intended for local development - without knowing what modifications you’ve made to the local dev compose setup to make it work in production it’s hard to guess what might be the problem (hence why it makes more sense imo to just use the pre-built published image :smiley:)

I’ll give it a shot in a controlled environment when I get a chance tomorrow. Last time I tried that something wasn’t working as expected and this had been working well for me for like a year or so.
The mods I made to the compose were missing to point to bind mounts rather than volume mounts.