theopenconversationkit / theopenconversationkit/tock-docker

Admin Web is not responding on version 26.3.1

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
27
Forks
36
Avg merge
5m
Merged PRs (30d)
1

Description

When following the instructions in the Readme

# get the last docker-compose-bot file
curl -o docker-compose-bot.yml https://raw.githubusercontent.com/theopenconversationkit/tock-docker/master/docker-compose-bot.yml
# get the script to start mongo in replicaset mode
mkdir -p scripts && curl -o scripts/setup.sh https://raw.githubusercontent.com/theopenconversationkit/tock-docker/master/scripts/setup.sh && chmod +x scripts/setup.sh
# get the last tag
curl -o .env https://raw.githubusercontent.com/theopenconversationkit/tock-docker/master/.env
# launch the stack
docker-compose -f docker-compose-bot.yml up

I just have to had this on mongo services as there is a memory issue or something related on Fedora

mongo:
    environment:
      - GLIBC_TUNABLES=glibc.pthread.rseq=1

Then, the stack starts successfully but when I open the Tock Studio homepage on http://localhost the page cannot be accessed. I am not seeing any errors in Docker services.

What’s strange is that when using CURL, a content is returned.

Do you have any ideas what's going wrong ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the README instructions and the downloaded docker-compose-bot.yml, scripts/setup.sh, and .env files. Run the stack on Fedora, compare the browser result at http://localhost with the content returned by curl, and inspect the Docker services; done means the Tock Studio homepage loads successfully without the extra environment workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, fedora
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.