![]() ![]() Note: between the different instruction links above, I did a test on $ echo $(uname -s)-$(uname -m) And that test returns Linux-x86_64 The instructions for cli version already had the flavor decoded, but note the L in Linux. (insert about an hour of different trials here.) The answer is to follow the cli-commands version. I believe I should be using the command line instruction version, correct? The installation for Docker Compose was pretty confusing. It will be difficult / impossible to make any assumptions about a user's configuration. So even with the above, I don't think we can resolve the "It requires changing the full environment of an unknown user." situation. For those, "document how to migrate from v1 to v2" would (I think) be the only solution. That package would be an optional install (user to opt-in), and that package could Conflict with distro packages (that we know of), but would probably not resolve the "manual" and "pip" installs. So yes, possibly a "compatibility" package could be created (although it would be just a script doing the same as an alias). rpm package managers will not be aware of that binary to be present. Things become more involved if the user has docker-compose installed from a binary or through pip, because the. deb packages, which means the package cannot be installed without uninstalling any existing docker-compose (which could be a distro package). While we (once stable) would like to see users migrate to v2, the v2 and v1 versions do not have to conflict (both can be used, and it's possible users have a reason to use the python version).Īdding the wrapper to the default package means we will have to add a Conflicts: or Deprecates: annotation to the. ![]() rpm packages, but some Linux distributions have. Docker itself has not shipped docker-compose. A separate "compatibility package" could be possible, but if docker-compose v1 is not deprecated, it should not come by default.įor Docker Desktop, the installation is somewhat more "opinionated", but for a Linux server install, things are more involved.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |