yuqi1129 opened a new issue, #137:
URL: https://github.com/apache/gravitino-playground/issues/137
### Version
main branch
### Describe what's wrong
When I start the playground in the EC2 instance, the following error occurs:
```
[ec2-user@ip-172-31-10-123 gravitino-playground]$ ./playground.sh start
[INFO] Starting the playground...
[INFO] The playground requires 2 CPU cores, 6 GB of RAM, and 25 GB of disk
storage to operate efficiently.
[INFO] Port status check results:
[INFO] Available ports: 6080 8090 9001 3307 19000 19083 60070 13306 15342
18080 18888 19090 13000
[INFO] Testing Docker environment by running hello-world...
[INFO] Docker check passed: Docker is working correctly!
Untagged: hello-world:linux
Untagged:
hello-world@sha256:a77ecd852b17bfaee6708208960645d20fc9e6d0eec12353f8eb0e7b94bb647a
Deleted:
sha256:74cc54e27dc41bb10dc4b2226072d469509f2f22f1a3ce74f4a59661a1d44602
Deleted:
sha256:63a41026379f4391a306242eb0b9f26dc3550d863b7fdbb97d899f6eb89efe72
[INFO] Docker compose check passed: Docker compose is working correctly
using docker compose command!
docker: 'compose' is not a docker command.
See 'docker --help'
[INFO] Docker disk check passed: 47 GB available.
[INFO] Docker RAM check passed: 7 GB available.
[INFO] Docker CPU check passed: 2 cores available.
[INFO] Preparing packages...
Downloading iceberg-spark-runtime-3.4_2.12-1.5.2.jar to
/home/ec2-user/gravitino-playground/init/spark/packages
Downloading gravitino-spark-connector-runtime-3.4_2.12-0.8.0-incubating.jar
to /home/ec2-user/gravitino-playground/init/spark/packages
Downloading mysql-connector-java-8.0.27.jar to
/home/ec2-user/gravitino-playground/init/spark/packages
Downloading kyuubi-spark-authz-shaded_2.12-1.9.2.jar to
/home/ec2-user/gravitino-playground/init/spark/packages
Downloading mysql-connector-java-8.0.27.jar to
/home/ec2-user/gravitino-playground/init/gravitino/packages
Downloading postgresql-42.2.7.jar to
/home/ec2-user/gravitino-playground/init/gravitino/packages
unknown shorthand flag: 'p' in -p
See 'docker --help'.
Usage: docker [OPTIONS] COMMAND
A self-sufficient runtime for containers
Common Commands:
run Create and run a new container from an image
exec Execute a command in a running container
ps List containers
build Build an image from a Dockerfile
pull Download an image from a registry
push Upload an image to a registry
images List images
login Log in to a registry
logout Log out from a registry
search Search Docker Hub for images
version Show the Docker version information
info Display system-wide information
Management Commands:
builder Manage builds
buildx* Docker Buildx (Docker Inc., v0.0.0+unknown)
container Manage containers
context Manage contexts
image Manage images
manifest Manage Docker image manifests and manifest lists
network Manage networks
plugin Manage plugins
system Manage Docker
trust Manage trust on Docker images
volume Manage volumes
Swarm Commands:
swarm Manage Swarm
Commands:
attach Attach local standard input, output, and error streams to a
running container
commit Create a new image from a container's changes
cp Copy files/folders between a container and the local filesystem
create Create a new container
diff Inspect changes to files or directories on a container's
filesystem
events Get real time events from the server
export Export a container's filesystem as a tar archive
history Show the history of an image
import Import the contents from a tarball to create a filesystem image
inspect Return low-level information on Docker objects
kill Kill one or more running containers
load Load an image from a tar archive or STDIN
logs Fetch the logs of a container
pause Pause all processes within one or more containers
port List port mappings or a specific mapping for the container
rename Rename a container
restart Restart one or more containers
rm Remove one or more containers
rmi Remove one or more images
save Save one or more images to a tar archive (streamed to STDOUT
by default)
start Start one or more stopped containers
stats Display a live stream of container(s) resource usage statistics
stop Stop one or more running containers
tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
top Display the running processes of a container
unpause Unpause all processes within one or more containers
update Update configuration of one or more containers
wait Block until one or more containers stop, then print their exit
codes
Global Options:
--config string Location of client config files (default
"/home/ec2-user/.docker")
-c, --context string Name of the context to use to connect to the
daemon (overrides DOCKER_HOST env var and default context set with "docker
context use")
-D, --debug Enable debug mode
-H, --host list Daemon socket to connect to
-l, --log-level string Set the logging level ("debug", "info", "warn",
"error", "fatal") (default "info")
--tls Use TLS; implied by --tlsverify
--tlscacert string Trust certs signed only by this CA (default
"/home/ec2-user/.docker/ca.pem")
--tlscert string Path to TLS certificate file (default
"/home/ec2-user/.docker/cert.pem")
--tlskey string Path to TLS key file (default
"/home/ec2-user/.docker/key.pem")
--tlsverify Use TLS and verify the remote
-v, --version Print version information and quit
Run 'docker COMMAND --help' for more information on a command.
For more help on how to use Docker, head to
https://docs.docker.com/go/guides/
[INFO] Check log details:
/home/ec2-user/gravitino-playground/playground-2025031308391741855140.log
```
### Error message and/or stacktrace
Please see above
### How to reproduce
[ec2-user@ip-172-31-10-123 gravitino-playground]$ uname -a
Linux ip-172-31-10-123.ap-northeast-1.compute.internal
6.1.102-111.182.amzn2023.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Aug 13 22:23:09 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
[ec2-user@ip-172-31-10-123 gravitino-playground]$ docker-compose -v
Docker Compose version v2.29.7
### Additional context
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
