Raspbery Pi docker / docker-compose

Andy Kutruff

Hey there. I'm trying to get triggercmd setup and running on a raspberry pi in headless mode inside a docker container. There aren't any arm64 builds on dockerhub, so I gave it a whirl myself. In general I need everything running in docker these days, so any help would be appreciated.

The environment variables don't appear to be respected, and it seems like there's a daemon install missing? I tried also using the raspberry pi deb directly but that was just getting weird.

TOKEN environment variable not found.  We'll prompt for a token.
COMPUTERID environment variable not found.  We'll create a new computer in the account.
COMMANDS environment variable not found.  We'll use the default commands.
Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot
Daemon install: false
No token exists.  Login to request one.

Docker files below

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get -y update \
    && apt-get -y upgrade \
    && apt install -y nodejs npm wget

RUN wget https://raw.githubusercontent.com/rvmey/TRIGGERcmd-Agent/master/ubuntupackage.json -O package.json
RUN npm install
RUN wget https://raw.githubusercontent.com/rvmey/TRIGGERcmd-Agent/master/src/agent.js
RUN wget https://raw.githubusercontent.com/rvmey/TRIGGERcmd-Agent/master/src/gd_bundle-g2-g1.crt
RUN wget https://raw.githubusercontent.com/rvmey/TRIGGERcmd-Agent/master/src/sendresult.sh
RUN wget https://raw.githubusercontent.com/rvmey/TRIGGERcmd-Agent/master/src/linuxcommands.json

COPY start.sh start.sh

CMD ./start.sh

docker-compose.yml

version: "3"
services:
  triggercmd:
    build: .
    image: triggercmd
    environment:
      - TOKEN=<redacted>
      - COMPUTERID=mycomputer
      - TZ=America/New_York
    volumes:
      - data:/root/.TRIGGERcmdData
    restart: always       
volumes:
  data: {}

Russ

@Andy-Kutruff, try this one. I just pushed it:

docker pull rvmey/triggercmdagent:arm

You'll need to create an actual computer record in your account and get the ID for it from your browser's address bar after you click view triggers.