Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Hello! Are you referring to couchdb right?

The easiest way is to just run the container as stated the docs:

docker run -p 5984:5984 -d couchdb:2.3.1

then you can access it via the web: http://localhost:5984/_utils/

I always run it like that. I don’t have a docker compose, but creating it should be quite easy, found this online, maybe you can use it as a guide?

Also note that there is a new version 3 that requires to set up a user and password before running the container

*************************************************************
ERROR: CouchDB 3.0+ will no longer run in "Admin Party"
       mode. You *MUST* specify an admin user and
       password, either via your own .ini file mapped
       into the container at /opt/couchdb/etc/local.ini
       or inside /opt/couchdb/etc/local.d, or with
       "-e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password"
       to set it via "docker run".
*************************************************************

hope it helps!

(+1)

thanks baj, i was considering doing it myself, but i thought id ask just incase you had already used one, best to get one from the original source if possible that way i know it will work correctly, but yeah i can make one . Thanks for the response!

hey did you ended up creating a docker compose after all?

i didnt, i am still in the middle of setting up a new server so i havent needed the server yet.

but i did how ever come across a bug im yet to solve with the app image. on my home system, when i run the app image i get a error regarding the sanbox permissions. i think that needs to be set. on my work system this worked as i have a different environment. but my home system(desktop) i cant get it to run.

This is the error i receive.

FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_drafftTREQd9/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

when my server is back online, ill take a look at a docker compose. script. but im still waiting on parts from the US. water damage after a flood is a nightmare.

Sad to hear about the flood damage! Hope everything is ok! I’ll set a docker compose and add it to the documentation as the “official” setup.

I’m not sure about your environment (are you running Debian?), bu maybe you can try:

Possible Solutions

  1. Run with No Sandbox (Quick Fix): ./drafft-appimagefile --no-sandbox
  2. Use the –disable-setuid-sandbox Flag: ./drafft-appimagefile –disable-setuid-sandbox

Or this? https://authmane512.medium.com/solve-the-suid-sandbox-helper-binary-was-found-but-is-not-configured-correctly-3-solutions-4f1425a9a76c

im using on my home system Tuxedo os with dual boot arch (arch is mainly used for me for experimenting with the kernel).thats based on ubuntu but runs kde environment. on my work system im using rhel.

the no sandbox doesnt always work, i tried that solution that refused to open the software, no errors just sat with a blank terminal line. has done that in a few other flatpaks, such as affine. and the set uid option i tested as well that gave me a segfault crash, no idea why, So far the only way i was able to get it running was to extract it. and set the sandbox to root. and add 4577 to it. it ran perfect after that.

that leads me to begin to question appimages in their current state. (as a whole not your product as it happening on a lot of other app images as well.) the problem with it is most people are not like myself, if it isnt a simple fix, they will simply move on to an alternative, they wont debug or try and solve it. thats one of the reasons i mention it here. i love the drafft software and want it to succeed.

also it happens for the portable version.

for the portable version this works to resolve it:

Download and extract.

cd ./draft-linux_portable
sudo chown root:root chrome-sandbox
sudo chmod 4577 chrome-sandbox
./drafft

and that will run correctly from any where

i am going to assume that it may work with an extracted app image. using –appimage-extract then using the same procedure but instead of folder name above its likely to be squashfs

but i havent tried that as im not home to test.

hm this issue leads me to apparmour profile again and also a strange case where the appimage has a space in the path.

do you have any space in your path? https://github.com/electron/electron/issues/44414 https://github.com/electron/electron/issues/41066

BTW: Electron builder 26 which have apparmour support/fix will be stable soon apparently.

no spaces in path on my end, its an interesting bug, because it doesnt effect every system or os, so i decided to test other random app images as well, and some have the issue and some dont, i hope they fix the bugs with it as i think app images are great (not so much for security but for ease of use) thats where flatpak is good, provided that people set their permissions correctly (to be fair they usually dont so devs just leave it loose to ensure it runs. its a pretty common set of issues that really needs standardisation. it varies so greatly between systems even apparmor features varies between distro’s. i think their should be enforcement of feature set minimums but alas there is not.

im trying to find ways around these issues in my spare time as well, so if anything pops up that immediately fixes it ill be sure to share it.

i dont how ever, recommend people start adding the userns clone to 1. it will open a can of security worms that most people cannot fix or configure making them vulnerable.