Creating an instance gives `cannot exec in a stopped state: unknown` error

[songnguxyz]

Describe the situation

Summary: Creating an instance gives cannot exec in a stopped state: unknown error

Description: This isn't fully documented anywhere, but installing everything from the beginning does not solve the issue.

Screenshots:

Steps to reproduce the issue (if applicable):

1. Installing dependencies with this:

   apt-get update
   apt-get upgrade -y
   for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg -y; done
   apt-get install ca-certificates curl -y
   install -m 0755 -d /etc/apt/keyrings
   curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
   chmod a+r /etc/apt/keyrings/docker.asc
   echo \
   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
   $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
   sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
   apt-get update
   sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin -y
   DOCKER_CONFIG=${DOCKER_CONFIG:-$HOME/.docker}
   mkdir -p $DOCKER_CONFIG/cli-plugins
   curl -SL https://github.com/docker/compose/releases/download/v2.29.1/docker-compose-linux-x86_64 -o $DOCKER_CONFIG/cli-plugins/docker-compose
   chmod +x $DOCKER_CONFIG/cli-plugins/docker-compose
   curl -fsL https://raw.githubusercontent.com/CanastaWiki/Canasta-CLI/main/install.sh | bash

2. Run canasta create -i <ANYTHINGUWANT> -n <DOMAIN> -w <WIKINAME> -a admin -o compose
3. Enter the wiki sysop's password as required
4. Wait for almost 3 minutes and still get the error above

Expected behavior

Canasta should be ready with no issue at all and ready to be served to users, accessing the specified domain direct you to the wiki's main page

System info

Please complete the following information:

• MediaWiki version: N O N E (not fully installed)
• Canasta CLI version: 13b43d8 (a.k.a LATEST)
• Installed extensions and versions: N O N E (not fully installed)
• Host operating system: Ubuntu 22.04 LTS
• Do you have sudo/root permissions on the host OS? - Yes (ssh-ed with root)

Sanity checks

• Have you checked the documentation on canasta.wiki for how to address this? Yes
• Have you checked prior issues on GitHub yet? Yes
• Are you following all Canasta approaches and have avoided doing things such as running docker exec directly on the container, removing the Caddy/Varnish containers, adding unauthorized files to the Docker container after startup, etc.? Yes

[songnguxyz]

uh... @yaronkoren? running docker logs on the problematic container shows that:

+ . /functions.sh
+ mountpoint -q -- /mediawiki
Folder /mediawiki contains important data and must be mounted to persistent storage!
+ echo 'Folder /mediawiki contains important data and must be mounted to persistent storage!'
+ isTrue ''
+ case $1 in
+ return 1
+ exit 1

[songnguxyz]

(and it was sudo-ed)

[songnguxyz]

Sanity check update: After starting up my Canasta repo for the first time, I am getting a "Error 503 Backend fetch failed / Guru Meditation" error. was found in the documentation, but the error by itself is not relevant to the main issue

[jakejellinek]

I ran a docker pull on my canasta instance today to update to latest. I'm using Ubuntu 22.04 also and am seeing the same errors in my container logs. I think this is a bug?

[songnguxyz]

I ran a docker pull on my canasta instance today to update to latest. I'm using Ubuntu 22.04 also and am seeing the same errors in my container logs. I think this is a bug?

what version have you use before this happened?

[jakejellinek]

I ran a docker pull on my canasta instance today to update to latest. I'm using Ubuntu 22.04 also and am seeing the same errors in my container logs. I think this is a bug?

what version have you use before this happened?

How do I determine this? (I have rolled back my VM so am currently running my previous "latest" version which is using MediaWiki version 1.39.6)

[songnguxyz]

I ran a docker pull on my canasta instance today to update to latest. I'm using Ubuntu 22.04 also and am seeing the same errors in my container logs. I think this is a bug?

what version have you use before this happened?

How do I determine this? (I have rolled back my VM so am currently running my previous "latest" version which is using MediaWiki version 1.39.6)

just run sudo canasta version

[yaronkoren]

Hi guys - just so you know, I'm monitoring this discussion, and we're looking into the issue. But any more information (like the exact version of the code) could indeed be helpful.

[jakejellinek]

I ran a docker pull on my canasta instance today to update to latest. I'm using Ubuntu 22.04 also and am seeing the same errors in my container logs. I think this is a bug?

what version have you use before this happened?

How do I determine this? (I have rolled back my VM so am currently running my previous "latest" version which is using MediaWiki version 1.39.6)

just run sudo canasta version

canasta version

2024/08/12 09:39:59 Using /etc/canasta for configuration... This is canasta: built at 2024-02-13 22:03:30 from git commit 24df936.

[jakejellinek]

I think it broke when I did a docker compose pull to upgrade it, I just tried with a canasta upgrade command and that seems to have worked? What is the difference here?