You shouldn’t make a habit of doing this, but here’s a link to a script that’ll inline task definitions, for the rare case when you want a one-off task definition.
Some notes on running Concourse from a linode box:
- You can run the
webcommand and the
workercommand on the same machine. The web machine can be on a 1GB ram linode, it doesn’t take that much resources.
- While doable on the 1GB ram plan, you should really run the workers on at least the 2GB ram plans. This is more for storage than anything else.
- Using a linode is a better plan long term over getting a NUC so long as you stay under the 16 GB plan. Depending on your usage, the other benefits (not having to care about hardware issues) might even extend this to that.
As with the other services I maintain, the setup is managed inside of an ansible playbook.
I discovered the hard way that using the 1GB “nanode” plan was not a good plan. The disk very quickly filled up, in addition to everything being slow as molasses. Once I migrated the machine to the 2GB plan, I ran into issues with the volume space not being resized (concourse creates a worker volume logical volume with
$TOTAL_DISK_SPACE - 10GB of space), then further issues with the system thinking that a volumes which were deleted in fact weren’t, etc.
See this issue
$CONCOURSE_WORK_DIR/garden-properties.json before each time a worker starts.
I ran in to this issue when “upgrading” the host my concourse installation used from ubuntu 19.10 to 20.04. (Linode recommends you “upgrade” by creating a new instance at the desired OS, and copying over the necessary files - I just set everything up again because it was faster/easier to do it that way).
Sometimes, firewall or dns rules interfere with your workers. I resolved this by doing two things:
- Specifying the
CONCOURSE_GARDEN_DNS_SERVERvariable to a specific dns server (I use 220.127.116.11 so I don’t have to rely on Google).
- If that doesn’t work, then it’s usually a firewall rule. If you use
fly intercepton any of the offending gets, and you can’t ping ANY IPs, then it’s usually an overly restrictive firewall rule. You can adjust these with
ufwon ubuntu (or
See this issue.
# On a machine with fly fly -t $TARGET land-worker -w $WORKER_NAME # On the worker sudo systemctl stop concourse_worker # Back to fly fly -t $TARGET prune-worker -w $WORKER_NAME # Back to the worker sudo umount -f /opt/concourse/work_dir/volumes sudo sync sudo losetup -d /dev/loop0 sudo rm -rf /opt/concourse/work_dir/volumes.img sudo reboot
Pruning the worker (which really only needs to happen before the reboot) tells concourse to ignore any volumes that may or may not exist. Invoking
land-worker may or may not actually do things.
I wrote something on this a few years back. Which is, of course, out of date (at least, in regard to houdini).
Here’s my current launchagent (
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>AbandonProcessGroup</key> <true/> <key>KeepAlive</key> <true/> <key>Label</key> <string>com.rachelbrindle.concourse.worker</string> <key>Nice</key> <integer>0</integer> <key>ProgramArguments</key> <array> <string>/Users/you/concourse/worker.sh</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/usr/local/var/log/concourse_darwin_worker.log</string> </dict> </plist>
And the corresponding worker.sh:
#!/bin/sh -l cd /Users/you/concourse /usr/local/bin/concourse worker \ --work-dir /Users/you/concourse/darwin_work_dir \ --tsa-host $CONCOURSE_HOST:2222 \ --tsa-public-key /Users/you/concourse/keys/web/tsa_host_key.pub \ --tsa-worker-private-key /Users/you/concourse/keys/worker/worker_key
Last updated: 2020-11-22 22:00:30 -0800