Common questions about build tools

Table of Contents:

My image is not being updated. Is it possible that you are not pulling the image from docker hub, every time you run the container?

In most cases, DeployBot doesn’t pull the image from docker hub each time. We try to do it as rarely as possible to allow for reproducible builds and keep deployment times predictable.
If you want to have more control over used image version, you can employ tags and specify them explicitly in the container name(i.e. ubuntu/ubuntu:14.04). If a container name changes, it will be downloaded again.

I reviewed the deployment logs but it just says that my commands can’t be found. What am I doing wrong?

It could be that the programs your running are not installed on our container. You can see what’s included in our container here. If what you’re running is not in our container by default, you’ll need to install them first before you can move forward. Please keep in mind you’re allowed to have full root access inside the container.

How can I find the Docker image or dockerfile for the container Deploybot is using?

Our container is public and you can find it here. We don't have any specific requirements for the container other than that it needs to have bash installed.

Is there an option where I can run DeployBot’s docker container on my server?

We don't have a feature to run our Docker containers on your servers. But we do offer shell deployments where you could connect to your server and run your commands directly there if you want to run the deployment on your server. We have a blog post and help article that discusses how to run shell deployments. 

DeployBot’s container doesn’t contain the packages I need. What can I do?

What you can do in these situations is create your own Docker container to use in DeployBot. Our help article on build tools includes instructions on that in the“Configuring your own containers” section on your server settings page. 

Does DeployBot support Git LFS?

Unfortunately, we do not yet support LFS by default. But it is possible to use Git LFS right now using build tools. Inside the container you are free to install the LFS plugin and set things up yourself. You could also use a command to install the LFS distribution.

Why does DeployBot run the“cache build commands” when files such as composer.json, package.json, etc haven’t been changed?

We have multiple servers in our deployment cluster and each of them needs to have your pre-built container cached. When your deployment hits a server that it never ran on before, it will trigger"cache build commands" script. 
We try to catch this before it happens and only execute your deployment on servers that you’ve deployed to already, but it's not always possible. If this is happening frequently, please reach out to our support team so that we can investigate. 

In most cases, DeployBot doesn’t pull the image from docker hub each time. We try to do it as rarely as possible to allow for reproducible builds and keep deployment times predictable.

If you want to have more control over used image version, you can employ tags and specify them explicitly in the container name(i.e. ubuntu/ubuntu:14.04). If a container name changes, it will be downloaded again.

Still need help? Contact Us Contact Us