vishalxl / nostr_console

Nostr console is an open-source twitter-like social network, direct chat app and group chat all bundled into one program. Built on the decentralized Nostr protocol.
GNU Affero General Public License v3.0
441 stars 33 forks source link

Docker: unable to prepare context #36

Closed vatavasi closed 1 year ago

vatavasi commented 1 year ago

I ran the given command to try nostr console - sudo docker build -t nostr_console .

But I keep getting the below error. unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/asinode/Dockerfile: no such file or directory

Docker is surely enabled and running when I checked systemctl status docker.

I ran all this from home folder (~). And the docker installation is fine.

$ 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)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

Below are the hidden files I have on the home folder. And there is no file such as Dockerfile as suggested in several other forums. Not sure if I am supposed to have this file within the home folder.

$ ll -a
-rw-------.  1 asinode asinode 9994 Dec 16 15:38 .bash_history
-rw-r--r--.  1 asinode asinode   18 Sep 27 18:25 .bash_logout
-rw-r--r--.  1 asinode asinode  141 Sep 27 18:25 .bash_profile
-rw-r--r--.  1 asinode asinode  492 Sep 27 18:25 .bashrc
drwxr-xr-x. 34 asinode asinode 4096 Dec 16 15:44 .cache
drwxr-xr-x. 31 asinode asinode 4096 Dec 16 15:49 .config
drwxr-xr-x.  6 asinode asinode 4096 Dec 16 15:23 .docker
drwx------.  3 asinode asinode 4096 Dec  6 17:52 .gnome
drwx------.  6 asinode asinode 4096 Dec  2 00:21 .gnupg
-rw-r--r--.  1 asinode asinode    0 Dec 16 15:42 .gtkrc-2.0
-rw-r--r--.  1 asinode asinode  321 Dec 16 15:42 .gtkrc-2.0-kde4
-rw-------.  1 asinode asinode   20 Dec 16 15:46 .lesshst
drwxr-xr-x.  4 asinode asinode 4096 Dec  1 22:39 .local
drwxr-xr-x.  5 asinode asinode 4096 Dec  1 22:41 .mozilla
drwx------.  3 asinode asinode 4096 Dec  1 23:19 .pki
drwxr-xr-x.  2 asinode asinode 4096 Dec  1 22:39 Public
drwxr-xr-x.  3 asinode asinode 4096 Dec  6 18:35 .shutter

drwx------.  4 asinode asinode 4096 Dec  2 00:21 .thunderbird

Is there any more info I need to provide here? Please see if you can advise a solution to this. Thanks.

vishalxl commented 1 year ago

You have to ckeck out or unzip the code. And then in that directory run that command, because the Dockerfile is in the project directory.

vatavasi commented 1 year ago

That was so silly of me not recognizing this. Apologies. But can I suggest the content be modified to just add the initial steps one should take before starting to use docker specific commands. Thanks anyway.

vishalxl commented 1 year ago

no problem, and yes, I'll mention that. even I am not that familiar with docker that much.