No, those are just warnings. For some reason docker-compose isn't picking up the .env.sample file. You are running docker-compose aren't you?

1 sats \ 2 replies \ @relc 21 Oct

i run: docker-compose up --build i have: ~/sn$ docker version Client: Docker Engine - Community Version: 20.10.9 API version: 1.41 Go version: go1.16.8 Git commit: c2ea9bc Built: Mon Oct 4 16:08:29 2021 OS/Arch: linux/amd64 Context: default Experimental: true

Server: Docker Engine - Community Engine: Version: 20.10.9 API version: 1.41 (minimum version 1.12) Go version: go1.16.8 Git commit: 79ea9d3 Built: Mon Oct 4 16:06:37 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.11 GitCommit: 5b46e404f6b9f661a205e28d59c982d3634148f8 runc: Version: 1.0.2 GitCommit: v1.0.2-0-g52b36a2 docker-init: Version: 0.19.0 GitCommit: de40ad0

~/sn$ docker-compose version docker-compose version 1.25.0, build unknown docker-py version: 4.1.0 CPython version: 3.8.10 OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020

i am using a different command before compose: git clone sn && cd sn because your command gives me:

:~$ git clone sn && cd sn Cloning into 'sn'... The authenticity of host ' (' can't be established. RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added ',' (RSA) to the list of known hosts. Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

i run several dockers on this machine for tests. with most containers there is a litte hickup here and there but i really like docker for testing now.

2 sats \ 1 replies \ @k00b OP 21 Oct

It’s not obvious to me what’s going wrong.

2 sats \ 0 replies \ @relc 21 Oct

we will fix it no worrys