Closed nativeit closed 2 years ago
Evidently 1.21.0-3
is the latest version available in the apt repos for Debian Buster. I found a workaround by manually installing Docker Compose according to the instructions at https://docs.docker.com/compose/install/. This brought me to version 1.29.2
, and resolved this issue.
Server Info (please complete the following information):
Installation Method:
Describe the bug After configuring
.env
file according to documentation, using the unmodifieddocker-compose.yml
linked in the documentation, issuingdocker-compose up -d
results in the following error:My software versions are as follows:
To Reproduce Steps to reproduce the behavior:
.env
according to Tactical RMM docsdocker-compose up -d
Expected behavior Docker Compose should pull images and run containers specified in
docker-compose.yml
Additional context I am not exactly an expert in Docker, however I have been running a Caprover server with dozens of Docker Compose based images for the last few years, and have had my own contributions of complex Caprover one-click-app templates accepted to their official app repository (incl. Redmine+MySQL, Redmine+PostgreSQL, Netbox, and contributed to other app templates like Corteza CRM/ERP and Invoice Ninja).
I only say this to demonstrate a solid foundational understanding of Docker and Docker Compose specs, and a high comfort level in writing Compose specifications with dynamic variables and advanced features. I will continue to troubleshoot this problem on my own, and will post back if I find the cause of the problem (or figure out where I went wrong). I am also happy to submit a PR if I find a fix that does not affect other features/functions in any other way if that would make the dev's lives easier.
Thank you so much for your work on this project, I am an eager supporter of this endeavor!