Can't get any of the example docker-compose images to work. about docker HOT 6 CLOSED

Can you paste your docker.yml file to check out?
If you need to use another port, select something random like 8183 or whatever.

Are you hosting this in the cloud, or locally?

from docker.

I uploaded it as text. I already have also uploaded .env since I'm using a DB local to the machine.

I'm running this (or attempting to) on my local machine. But because I have 4-5 other docker instances running + calibre (which insists on using 8080 as the port) I need a different port. I picked 7500 and 7501 at random.

I should mention that at one point I did get the simple system working using http:// and it connected to the DB, but Firefox wouldn't allow normal http access, but I could see the registration page with lynx (cmdline web browser).

from docker.

Well, it looks like you are running a far more complex setup here than the average person.

Is there any reason you need a proxy, and to be pushing all these certs, and a queue, and redis? Like, this should really just be 2 containers and off you go. You can try to look at the various log files for each of these containers and see if there's any clues, but really - the YML seems relatively fine without combing through it extensively.

For reference, here's my docker-compose. It's really all you need.....

version: "3.4"

services:
  app:
    image: monica
    depends_on:
      - db
    ports:
      - 8156:80
    environment:
      - APP_KEY=t1YmI32wWPnZz9z8Dj8k20NFaDHG7kyh
      - DB_HOST=db
      - DB_USERNAME=monica
      - DB_PASSWORD=249e%66igjRe@pMY
    volumes:
      - /volume1/docker/monica/html:/var/www/html/storage
    restart: always

  db:
    image: mysql:5.7
    environment:
      - MYSQL_RANDOM_ROOT_PASSWORD=R!d&dW%k!9sT9Gwe
      - MYSQL_DATABASE=monica
      - MYSQL_USER=monica
      - MYSQL_PASSWORD=249e%66igjRe@pMY
    volumes:
      - /volume1/docker/monica/mysql:/var/lib/mysql
    restart: always

volumes:
  data:
    name: data
  mysql:
    name: mysql

Like, you can copy and paste what I have there, and you'd be running on port 8156. Granted, those passwords have been modified from what they actually are. I would suggest when you attach code, you scrub it for your passwords and login names. One of your files reveals some information I don't think you would generally want anyone to see. Please consider taking it down or maybe modifying your attachments ;)

Anyways, try my docker compose file. Just toss that into a new stack with Portainer and you'll be up. If you need certs or whatever, you should be able to create those in whatever containers handle the certs and your reverse proxy.

from docker.

I tried your docker-compose.yml unchanged and it gives me the same issue I had with the simple example (amd most of the others). Firefox will not play with it.

Secure Connection Failed

An error occurred during a connection to localhost:8156. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

This is the reason I went down the whole SSL rabbit hole in the first place. sigh

from docker.

You shouldn't be getting any SSL issues as you're not using SSL in any way here. I can only think you're making this way more complicated than it needs to be, or you're doing something that you're not mentioning here.

You're installing this on a local box, right? Let's for example say your device that holds your docker instance is 192.168.1.50.
Once the container has been deployed, use your browser and go to http://192.168.1.50:8156

It sounds like you've got something installed on the host machine that's trying to intercept traffic or you've got some funky SSL stuff happening when none of that should be touching your connection.

EDIT - I see you're doing this on your LOCAL machine?! OK. It should literally just be http://localhost:8156 once the container has been deployed. If that doesn't work, you've clearly got something installed that is intercepting traffic or doing some sort of funky redirects.

from docker.

It seems the problem was with trying to use localhost. When I used the IP address it worked. Thanks!

from docker.