Null User Object

  • 63 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle

































  • Ok, that definitely helped. It now seems to run without errors…

    Creating lemmy_pictrs_1   ... done
    Creating lemmy_postgres_1 ... done
    Creating lemmy_lemmy_1    ... done
    Creating lemmy_lemmy-ui_1 ... done
    Creating lemmy_proxy_1    ... done
    

    But, then it just drops back to the command line. The docs say You can access the lemmy-ui at http://localhost:80, however, running a browser directly on the VM that lemmy is (supposedly) running on, and going to any of localhost:80, 127.0.0.1:80, the.machine.ip:80, all say unable to connect.

    Seems to be running?

    $ ps -ef | grep lemmy
    avahi        613       1  0 02:47 ?        00:00:02 avahi-daemon: running [lemmy.local]
    root       28970   28950  0 08:29 ?        00:00:00 /app/lemmy
    70         29018   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33172) idle
    70         29019   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33182) idle
    70         29020   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33188) idle
    70         29022   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33194) idle
    70         29024   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33204) idle
    70         29025   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33212) idle
    70         29026   27950  0 08:29 ?        00:00:00 postgres: lemmy lemmy 172.19.0.3(33216) idle
    

    Any tips on where to find logs, etc? I’m not even sure where it downloaded everything to, as it’s not in the lemmy folder that the instructions had me create.

    ETA: netstat -lp doesn’t seem to show it listening on any ports.


  • Well, that seems to have gotten a bit further, at least.

    Pulling lemmy (dessalines/lemmy:0.17.4)...
    0.17.4: Pulling from dessalines/lemmy
    8a49fdb3b6a5: Pull complete
    0de2c9bbcc62: Pull complete
    0f4c460d690c: Pull complete
    Digest: sha256:7aa2f62bf3217191797e374a6aa283b77d13632db2922335d0430029beb53b1d
    Status: Downloaded newer image for dessalines/lemmy:0.17.4
    Pulling lemmy-ui (dessalines/lemmy-ui:0.17.1)...
    0.17.1: Pulling from dessalines/lemmy-ui
    8921db27df28: Pull complete
    361849a0fe60: Pull complete
    4769d5fe84bb: Pull complete
    1a33b52da743: Pull complete
    b50526249338: Pull complete
    cdece431b19a: Pull complete
    Digest: sha256:b45e296a82c308c3839f3ce676df3b852aab519e21bd3d7b38e8d0064e95d25e
    Status: Downloaded newer image for dessalines/lemmy-ui:0.17.1
    Pulling proxy (nginx:1-alpine)...
    1-alpine: Pulling from library/nginx
    4db1b89c0bd1: Pull complete
    bd338968799f: Pull complete
    6a107772494d: Pull complete
    9f05b0cc5f6e: Pull complete
    4c5efdb87c4a: Pull complete
    c8794a7158bf: Pull complete
    8de2a93581dc: Pull complete
    768e67c521a9: Pull complete
    Digest: sha256:2d194184b067db3598771b4cf326cfe6ad5051937ba1132b8b7d4b0184e0d0a6
    Status: Downloaded newer image for nginx:1-alpine
    Creating lemmy_postgres_1 ... error
    Creating lemmy_pictrs_1   ... 
    
    ERROR: for lemmy_postgres_1  Cannot create container for service postgres: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.CCreating lemmy_pictrs_1   ... error
    
    ERROR: for lemmy_pictrs_1  Cannot create container for service pictrs: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
    
    ERROR: for postgres  Cannot create container for service postgres: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
    
    ERROR: for pictrs  Cannot create container for service pictrs: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
    ERROR: Encountered errors while bringing up the project.