32 replies

Tried to update... bot not responding

✅Solved

I just tried to update and now my bot isn't responding on Telegram. This is what we did. I'm running OC locally on my macbook inside a docker container...

damonborozny@Damons-Laptop ~ % docker pull ghcr.io/openclaw/openclaw:latest
docker stop openclaw-local && docker rm openclaw-local

then recreate it with your usual run/compose command using the same mounts/env

latest: Pulling from openclaw/openclaw
8578011282ae: Pull complete
443d4217b87a: Pull complete
a3d27b842bb7: Pull complete
869fdd20a733: Pull complete
d09a8402a034: Pull complete
7b02835e7252: Pull complete
e31e23dde45d: Pull complete
dfe2766e06f3: Pull complete
323cc0f6bf2f: Pull complete
215985bb00bb: Pull complete
1deefd9dcc8d: Pull complete
8181812d8279: Pull complete
431afc681bb3: Pull complete
ccb7de8cba98: Pull complete
dc73482b6b1e: Pull complete
c768b14537a9: Pull complete
526eb68e42c6: Pull complete
1e1626a3e2e3: Pull complete
e5e6d8b19f8e: Pull complete
4f4fb700ef54: Pull complete
194a2f14d619: Pull complete
Digest: sha256:70c5677580a958f704eb27297a62661b501534c3b2b9dec7a61e5ed5aa0c24cf
Status: Downloaded newer image for ghcr.io/openclaw/openclaw:latest
ghcr.io/openclaw/openclaw:latest
openclaw-local
openclaw-local
zsh: command not found: #

and now I'm getting this:
damonborozny@Damons-Laptop ~ % docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
damonborozny@Damons-Laptop ~ % docker logs --tail 200 openclaw-local
Error response from daemon: No such container: openclaw-local

Solution

In that case, do:

docker compose pull
docker compose up -d
docker compose logs -f --tail 200

docker compose pull
docker compose up -d
docker compose logs -f --tail 200

2) If there is no compose file: inspect the backup tarball for

openclaw.json

openclaw.json

Run:

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz | head -80

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz \
  | grep -E "openclaw\\.json$|/\\.env$" || true

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz | head -80

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz \
  | grep -E "openclaw\\.json$|/\\.env$" || true

Paste that output (it’s just filenames). Once we see where

openclaw.json

openclaw.json

is inside the tarball, I’ll tell you the exact

tar -xzf ...

tar -xzf ...

command (with the right

--strip-components

--strip-components

if needed) and the exact

docker run ... -v <restored>:/home/node/.openclaw ...

docker run ... -v <restored>:/home/node/.openclaw ...

to bring your Telegram bot back.

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2d ago•

32 replies

damon129

Tried to update... bot not responding

✅Solved

then recreate it with your usual run/compose command using the same mounts/env

Solution

In that case, do:

docker compose pull
docker compose up -d
docker compose logs -f --tail 200

docker compose pull
docker compose up -d
docker compose logs -f --tail 200

2) If there is no compose file: inspect the backup tarball for

openclaw.json

openclaw.json

Run:

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz | head -80

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz \
  | grep -E "openclaw\\.json$|/\\.env$" || true

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz | head -80

tar -tzf /Users/damonborozny/desktop/OC_Shared/special-reports/backups/20260308-163948/openclaw-instance-20260308-163948.tgz \
  | grep -E "openclaw\\.json$|/\\.env$" || true

Paste that output (it’s just filenames). Once we see where

openclaw.json

openclaw.json

is inside the tarball, I’ll tell you the exact

tar -xzf ...

tar -xzf ...

command (with the right

--strip-components

--strip-components

if needed) and the exact

docker run ... -v <restored>:/home/node/.openclaw ...

docker run ... -v <restored>:/home/node/.openclaw ...

to bring your Telegram bot back.

Jump to solution

Tried to update... bot not responding

then recreate it with your usual run/compose command using the same mounts/env

2) If there is no compose file: inspect the backup tarball for
`openclaw.json`
`openclaw.json`

Tried to update... bot not responding

then recreate it with your usual run/compose command using the same mounts/env

2) If there is no compose file: inspect the backup tarball for
`openclaw.json`
`openclaw.json`

Similar Threads

Similar Threads

Similar Threads

Tried to update... bot not responding

then recreate it with your usual run/compose command using the same mounts/env

2) If there is no compose file: inspect the backup tarball for openclaw.jsonopenclaw.json

Tried to update... bot not responding

then recreate it with your usual run/compose command using the same mounts/env

2) If there is no compose file: inspect the backup tarball for openclaw.jsonopenclaw.json

Similar Threads

Similar Threads

Similar Threads

2) If there is no compose file: inspect the backup tarball for
`openclaw.json`
`openclaw.json`

2) If there is no compose file: inspect the backup tarball for
`openclaw.json`
`openclaw.json`