Inexperienced user here, with the following few lines of transcript to seed discussion:
# ./launcher enter app
x86_64 arch detected.
WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed
Please be patient
2.0.20240602-0023: Pulling from discourse/base
728328ac3bde: Extracting [=============================> ] 18.68MB/31.43MB
1c0ca3c0af81: Download complete
...
This is not what I expected to happen.
Entering the command docker ps
shows me that there is a container with some flavour of Discourse already running. All I want to do is get a shell in that running container … not to rebuild the whole app. Indeed, inside the ./launcher
script (around line 746) it looks like the enter
command for ./launcher
is supposed to eventually do what I did expect … namely, issue the command
docker exec -it app /bin/bash
Is there a compelling reason to do a bunch of other work before doing this? If so, please enlighten me; if not, perhaps someone with experience and skill can transform this question into a useful suggestion. Thanks.