Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Yep, I have the same error. Everything until http://archive.ubuntu.com quantal-security works fine, then starting with quantal/main amd64 the 404s come in spades. The server itself, as it seems, uses different set of repositories, so apt-get update works fine.
Edit: You may try to use sources from /etc/apt/sources.list on your server, by specifying those in apt-repositories, in your repo.
Quick and dirty hack:
/etc/apt/sources.list) to your apt-repositories /var/lib/dokku/plugins/dokku-aptpre-build:if [ -f $DIR/apt-repositories ]; then
apt-get update
apt-get install -y software-properties-common
cat "$DIR/apt-repositories" | while read repository; do
add-apt-repository -y "\$repository"
done
fi
with the following:
if [ -f $DIR/apt-repositories ]; then
cat $DIR/apt-repositories > /etc/apt/sources.list
apt-get update
apt-get install -y software-properties-common
fi
cd -
dokku plugins-install
This has been confirmed to be a bug in Dokku. You can view the issue on GitHub.
Upgrading buildstep will resolve the problem:
$ git clone https://github.com/progrium/buildstep.git
$ cd buildstep
$ git pull origin master
$ sudo make build