is the datahub-actions image not buildable at our ...
# all-things-deployment
b
is the datahub-actions image not buildable at our end, ie, we must always pull it? Because i'm building my own containers in intranet and need to be careful not to pull the wrong version of action especially when its always pointing to head. Being able to build my own ensures that head doesnt go out of sync with the rest of the containers. Because I only see an option to pull in docker-compose.yml
a
You can always modify the docker-compose.yml file as you wish. If you want to use your local image, then replace the
datahub:head
image with yours.
b
yup, but its easier to keep track simply by building all the containers together
e
cc @big-carpet-38439 to set version on datahub-actions to avoid this issue
Ah so v0.0.1-beta.8 is the last stable deploy @better-orange-49102
we will start doing regular releases going forward
you can point to this image tag for now
b
hmmm i think we'll most likely pull from head but give it a specific date tag when we bring the image into intranet. we don't use releases because we want to retain the git history of the datahub repo.