Conversation

Notices

1. musicman (musicman@nu.federati.net)'s status on Friday, 24-Apr-2020 11:39:41 EDT musicman
   I feel like it should not take 3 minutes to start a container, but here we are
   
   CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
   aa64903e3436 40bbd906c968 "/assets/wrapper" 3 minutes ago Up 3 minutes (health: starting) 22/tcp, 443/tcp, 0.0.0.0:5555->80/tcp priceless_haibt
   1. musicman (musicman@nu.federati.net)'s status on Friday, 24-Apr-2020 11:41:15 EDT musicman

      in reply to
      I can see from docker logs -f though that the container is actually still doing stuff.
   2. musicman (musicman@nu.federati.net)'s status on Friday, 24-Apr-2020 11:42:19 EDT musicman

      in reply to
      woohoo! I did it. So, my problem yesterday was idk how many fold, but I thought I had started the container not on port 80 but it turns out I did start it on port 80 and the host is already listening on port 80.
      1. musicman (musicman@nu.federati.net)'s status on Friday, 24-Apr-2020 11:44:18 EDT musicman

         in reply to
         so, now the question is, does this image from docker hub already have volumes set up? The whole thing is pretty useless without a volume
   3. musicman (musicman@nu.federati.net)'s status on Friday, 24-Apr-2020 11:45:54 EDT musicman

      in reply to
      yikes. heptapod still has the gitlab branding