[Compose] Container never starts

[UntouchedWagons]

Affected Version

Don't know, container never starts

Describe the bug

Container doesn't start

Steps To Reproduce
Steps to reproduce the behavior:

1. Run docker compose up
2. Nothing happens

Expected behavior

The container to start

Reproduction rate
100%

Screenshots

Host System Information (where ispy agent is running/hosted):

• OS: Ubuntu 22.04

Additional Information

version: '3.3'
services:
  ispyagentdvr:
    ports:
      - '8090:8090'
      - '50000-50010:50000-50010/udp'
    volumes:
      - ispyagentdvr-commands:/agent/Commands/'
      - ispyagentdvr-data:/agent/Media/XML/'
      - ispyagentdvr-media:/agent/Media/WebServerRoot/Media/'
    environment:
      - TZ=America/Toronto
    container_name: ispyagentdvr
    image: doitandbedone/ispyagentdvr
    networks:
      - default
      - docker_default

volumes:
  ispyagentdvr-data:
  ispyagentdvr-commands:
  ispyagentdvr-media:

networks:
  default:
  docker_default:
    external: true

[UntouchedWagons]

ispyagentdvr-media is an NFS volume which would normally use my real name, but the other two volumes are bog standard volumes that docker manages for me.

[doitandbedone]

Not very familiar with them. However does seem like your problem is a configuration issue. Found this on stackoverflow: https://stackoverflow.com/questions/45282608/how-to-directly-mount-nfs-share-volume-in-container-using-docker-compose-v3#tab-top Have you used them on other containers before?

…

On Thu, Jan 5, 2023, 4:16 PM UntouchedWagons ***@***.***> wrote: ispyagentdvr-media is an NFS volume which would normally use my real name, but the other two volumes are bog standard volumes that docker manages for me. — Reply to this email directly, view it on GitHub <#537 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AORTFNGW27ZVNXEDUHQKC2LWQ5P5HANCNFSM6AAAAAATSQD3WQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[UntouchedWagons]

I have another docker stack with NFS backed docker volumes that work fine.

[UntouchedWagons]

No there's nothing at all, the screenshot I included in the opening comment is all I get.

[doitandbedone]

Never ran the image in compose. Will have to run it as barebones as possible though.

[doitandbedone]

Used Composerize and got this yaml file:

version: '3.3'
services:
    ispyagentdvr:
        ports:
            - '8090:8090'
            - '3478:3478/udp'
            - '50000-50010:50000-50010/udp'
        volumes:
            - '/appdata/ispyagentdvr/config/:/agent/Media/XML/'
            - '/appdata/ispyagentdvr/media/:/agent/Media/WebServerRoot/Media/'
            - '/appdata/ispyagentdvr/commands:/agent/Commands/'
        environment:
            - TZ=America/Los_Angeles
        container_name: ispyagentdvr
        image: doitandbedone/ispyagentdvr

Take notice at the single quotes for volumes. Seems you are missing the opening ones. Also missing the UDP port. The second volumes statement again seems like it's missing entries as per the prebious link I posted too.

[UntouchedWagons]

Well that's embarrassing. But even after fixing the quotes the container still won't start

version: '3.3'
services:
  ispyagentdvr:
    container_name: ispyagentdvr
    image: doitandbedone/ispyagentdvr
    restart: unless-stopped
    ports:
      - '8090:8090'
      - '50000-50010:50000-50010/udp'
    volumes:
      - 'ispyagentdvr-commands:/agent/Commands/'
      - 'ispyagentdvr-data:/agent/Media/XML/'
      - 'ispyagentdvr-media:/agent/Media/WebServerRoot/Media/'
    environment:
      - 'TZ=America/Toronto'
    networks:
      - default
      - docker_default

volumes:
  ispyagentdvr-data:
  ispyagentdvr-commands:
  ispyagentdvr-media:

networks:
  default:
  docker_default:
    external: true

I can't forward port 3478 because my Unifi controller is using it for... something,

[ispysoftware]

if it doesn't have 3478 it won't work. That's the port the stun server listens on and without stun you won't be able to connect to it.

[MrSiO]

Hi.
I saw you try to start the container using that command:

docker compose up

Just to make sure, you have to do the following commands in that order:

docker-compose create
docker-compose start

Make sure to use the dash "-" between docker and compose.

(you might get a warning that Start is depricated but it should start anyway)

Also,
I'm basically running the same compose you do but on version 3.5 and no quotes at all on volumes. Might wanna try.

[doitandbedone]

@UntouchedWagons did you try @MrSiO suggestion?

[UntouchedWagons]

docker compose up is fine when using the compose plugin. I'm going to keep using Blue Iris.