search

terminusdb / terminusdb-bootstrap

TerminusDB Bootstrap
https://terminusdb.com/
Apache License 2.0
66 stars 12 forks source link

Unable to run the container with podman on Fedora 35 #23

Closed montaropdf closed 2 years ago

montaropdf commented 2 years ago

Describe the bug With podman, on Fedora 35, the terminusdb container refuse to start and the following message is displayed in the terminal.

To use podman I followed the example in the README documentation.

Error: short-name resolution enforced but cannot prompt without a TTY

Is the container already running?

The container is definitively not running. According to https://github.com/containers/podman/issues/11530, this could be an issue with the script that start the container.

To Reproduce Steps to reproduce the behavior:

  1. Open a terminal
  2. Go to the directory containing the code of this repository
  3. Execute command ./terminusdb-container run
  4. See error

Expected behavior The container must start and be available according tohe configuration defined in the ENV file

Screenshots /

System information (please complete the following information):

Additional context Content of my ENV file

# shellcheck shell=sh
# shellcheck disable=SC2034

#
# ENVIRONMENT
#
# To persist environment settings copy this file to ENV
#

# Docker command
#TERMINUSDB_DOCKER=sudo docker
TERMINUSDB_DOCKER=podman

# Container
#TERMINUSDB_CONTAINER=terminusdb-server
#TERMINUSDB_REPOSITORY=terminusdb/terminusdb-server
#TERMINUSDB_NETWORK=bridge
#TERMINUSDB_LABEL_FILE=labels

# Version
TERMINUSDB_TAG=v10.0.13

# Name of Docker Storage Volume
#TERMINUSDB_STORAGE=terminusdb_storage_local

# Container Port to Publish
TERMINUSDB_PORT=6363

# Local Directory to Mount inside Container
#TERMINUSDB_LOCAL=/home/username/localfiles

# URL To TermiunusDB Console
#TERMINUSDB_CONSOLE_BASE_URL=//127.0.0.1:3005

# Server
#TERMINUSDB_AUTOLOGIN_ENABLED=false
TERMINUSDB_PASS=root
TERMINUSDB_SERVER_IP=127.0.0.1
TERMINUSDB_CONSOLE=http://127.0.0.1:6363/console

# HTTPS
TERMINUSDB_HTTPS_ENABLED=false
#TERMINUSDB_SSL_CERT=/etc/letsencrypt/live/example.com/fullchain.pem
#TERMINUSDB_SSL_CERT_KEY=/etc/letsencrypt/live/example.com/privkey.pem

# vim:ft=sh
rrooij commented 2 years ago

Does it work when you try the full image path?

Change:

#TERMINUSDB_REPOSITORY=terminusdb/terminusdb-server

To:

TERMINUSDB_REPOSITORY=terminusdb.docker.scarf.sh/terminusdb/terminusdb-server
rrooij commented 2 years ago

By the way, we are at version 10.0.15 now so you might want to update your ENV file. :smile:

montaropdf commented 2 years ago

Unfortunatelly, I still encounter the same problem.

spl commented 2 years ago

@montaropdf This worked for me with podman version 3.4.4 on Ubuntu 22.04:

TERMINUSDB_DOCKER=podman ./terminusdb-container run

What do you get when you run this?

podman pull terminusdb.docker.scarf.sh/terminusdb/terminusdb-server
matko commented 2 years ago

Closing as part of our issue cleanup, since it was not reproducible on ubuntu with podman. If this is still an issue on Fedora, leave a comment to notify us.