I'm deploying a new install on Docker / OSS home l...
# replication-ask-ai
j
I'm deploying a new install on Docker / OSS home lab and getting this error: Error response from daemon: manifest for airbyte/airbyte-api-server:0.50.9 not found: manifest unknown: manifest unknown
k
A message from kapa.ai
Based on the information provided in the extracts, it seems like you might be encountering a similar issue to what some users have reported on the Airbyte Slack channel. The error message you're seeing typically indicates that Docker is unable to find the specified image tag in the Docker registry. One possible solution could be to try running the command without specifying the version. For example, instead of using
VERSION=0.50.9 docker-compose up
, you could try just
docker-compose up
. This was a solution found by a user who was deploying Airbyte on a Mac M1 machine, as seen in this [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1669735769154519). Another user on a Mac M1 machine encountered a similar issue and was advised to ensure that Docker has enough space and to try running
docker system prune
to clean up unused Docker resources, as seen in this [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1671139885923699). If these solutions don't work, it would be helpful to check if you're following the correct version of the Airbyte documentation. The correct version can be found [here](https://docs.airbyte.com/deploying-airbyte/local-deployment). If you're still encountering issues, I would recommend reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) for further assistance.
j
Did not work, sadly
k
@Jeffrey Hunt I also got the same error. If you replace 0.50.9 with 0.50.8 in the part where the version is specified at the beginning of run-ab-platform.sh, it worked.
Copy code
VERSION=0.50.9
↓
VERSION=0.50.8
The version number may be cached in the .env file, so I think it would be good to fix that too if necessary.
j
@Kodai Saito, I tried that last night as well. Oddly enough it did finally run this morning but lots of docker errors for the API-SERVER container.
FYI, I had to do this for mine to work after the 0.50.10 update was posted: https://github.com/abiosoft/colima/issues/687
k
@Jeffrey Hunt Thanks for sharing the information. I will try it when I upgrade the version.