Docker-compose.yml is missing

Hello, everybody,

I have installed Ubuntu in VM ware.

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 18.04.1 LTS

Release: 18.04

Code name: bionic

In my Ubuntu I have installed DockerCE and Docker Compose

help.bitwarden.com/article/install-on-premise/

i greate an installation id and the key from bitwarden

When I input sudo docker run hello-world the output comes: is the output:

sudo docker run hello-world

Hello from Docker!

This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

  1. The Docker client contacted the Docker daemon.

  2. The Docker daemon pulled the "hello-world" image from the Docker Hub.

(amd64)

  1. The Docker daemon created a new container from that image which runs the

executable that produces the output you are currently reading.

  1. The Docker daemon streamed that output to the Docker client, which sent it

to your terminal.

……

Input docker-compose --version, I get the following output: docker-compose version 1.23.1, build b02f1306

I have successfully installed both of them.

Then I give Input:

curl -s -o bitwarden.sh \

<font color="#ffff00">Sync by honeybunny <font color="#ffff00"> raw.githubusercontent.com/bitwarden/core/master/scripts/bitwarden.sh

&& chmod +x bitwarden.sh

and he wants to have a domain name as well as creating it certificate I need to confirm and specify a mail. Everything fits too.

Using default tag: latest

latest: Pulling from certbot/certbot

Digest: sha256:3c82c0b8f2902248cf29dda038e26087ede1a7e491ccae1ff47901b2232b1fae

Status: Image is up to date for certbot/certbot:latest

Saving debug log to /etc/letsencrypt/logs/letsencrypt.log

Plugins selected: Authenticator standalone, Installer None

Obtaining a new certificate

Performing the following challenges:

01 challenge for bw.one-it.de

Waiting for verification…

Cleaning up challenges

Failed authorization procedure. bw.firma.de (01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for bw.one-it.de

IMPORTANT NOTES:

  • The following errors were reported by the server:

Domain: bw.one-it.de

Type: None

Detail: DNS problem: NXDOMAIN looking up A for bw.name.de

I will start Bitwareden

./bitwarden.sh

I get the following error message appears:

sudo ./bitwarden.sh start


| |__ () |__ ____ _ _ __ __| | ___ _ __

| '_ | | __\ \ /\ / / | '__/ _ |/ _ \ ’ \

| |) | | | \ V V / (| | | | (| | __/ | | |

|.__/||_| _/_/ _,|| _,|___|| ||

Open source password management solutions

Copyright 2015-2018, 8bit Solutions LLC

bitwarden.com, github.com/bitwarden

===================================================

Docker version 18.09.0, build 4d60db4

docker-compose version 1.23.1, build b02f1306

ERROR: .FileNotFoundError: [Errno 2] No such file or directory: ‘/home/bitwarden/bwdata/docker/docker-compose.yml’

I have search the tile docker-compose.yml and I have see the Directory docker is missing?

Why?What is the failure?

Take a look at the error in the middle:

Failed authorization procedure. bw.firma.de (01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for bw.one-it.de

Looks like you’re trying to request a certificate for an hostname that doesn’t exist in DNS?

Either try to use a hostname that actually resolves to the Bitwarden server IP or use your own certificate rather than the Lets Encrypt on in case the Bitwarden instance is internal.

Hi der Platzhalter “Firma” steht für unseren Firmennamen. Das hat nichts damit zu tun, den Hostnamen gibt es…

Hi Sebastian,

the error message itself complains about LetsEncrypt not being able to resolve the hostname you’re trying to work with:

Detail: DNS problem: NXDOMAIN looking up A for bw.name.de

It doesn’t really matter if you redacted the actual hostnames in question. The error message is coming from LetsEncrypt.

You can countercheck by trying to lookup the hostname you’re working with at a public (Google) resolver:

$ dig bw.name.de/bw.one-it.de @8.8.8.8

I have the same problem with the “docker-compose.yml”.

What is the solution to this problem?