docker-archive / compose-cli

Easily run your Compose application to the cloud with compose-cli
Apache License 2.0
956 stars 254 forks source link

Docker compose does not exist after successful install via script in Amazon ECS-optimized AMI #2199

Open ketozhang opened 1 year ago

ketozhang commented 1 year ago

Description

Steps to reproduce the issue:

  1. Launch an ECS-optimize AWS AML2 instance.
  2. Run curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/install/install_linux.sh | sh
  3. Call on docker compose

Describe the results you received:

sh-4.2$ curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/install/install_linux.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Running checks...
100  5982  100  5982    0     0  81902      0 --:--:-- --:--:-- --:--:-- 83083
Warning: This script has been tested on Ubuntu and may not work on other distributions
Checks passed!
Downloading CLI...
Downloaded CLI!
Installing CLI...
Done!
sh-4.2$ docker compose
docker: 'compose' is not a docker command.
See 'docker --help'
sh-4.2$ docker-compose
sh: docker-compose: command not found
sh-4.2$ exec $SHELL
$ docker-compose
bash: docker-compose: command not found
$ docker compose
docker: 'compose' is not a docker command.
See 'docker --help'
$ which docker
/usr/local/bin/docker
$

Describe the results you expected:

Docker compose should exist

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Docker version 20.10.13, build a224086

Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.

default

Output of docker info:


Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 2
 Server Version: 20.10.13
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 9cc61520f4cd876b86e77edfeb88fbcd536d1f9d
 runc version: f46b6ba2c9314cfc8caae24a32ec5fe9ef1059fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.14.287-215.504.amzn2.x86_64
 Operating System: Amazon Linux 2
 OSType: linux
 Architecture: x86_64
 CPUs: 1
 Total Memory: 982.3MiB
 Name: REDACTED
 ID: KLYC:AH5O:BCHU:I732:7KWA:UYJA:Q2NU:XM6B:BU2X:4SG2:KCQI:6T2B
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false```

**Additional environment details (AWS ECS, Azure ACI, local, etc.):**
qwetboy10 commented 1 year ago

Hi. I'm a student at UT Austin who is currently taking a virtualization class. Could I work on this issue as part of a school project? Thank you