[GH-ISSUE #784] How to use docker for #359

Closed
opened 2026-02-26 10:32:06 +03:00 by kerem · 4 comments
Owner

Originally created by @1n5aN1aC on GitHub (Dec 21, 2024).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/784

Not exactly a bug, but probably a lack of understanding, and unable to find direction in the documentation.

I wished to start with something very similar to the built-in example, (ds:example) so I started the docker container using docker-compose:

  onlyoffice:
    container_name: onlyoffice
    image: onlyoffice/documentserver
    restart: always
    ports:
      - "1005:80"
    environment:
      JWT_SECRET: example_jwt_secret
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /docker/onlyoffice/files:/var/lib/onlyoffice
      - /docker/onlyoffice/db:/var/lib/postgresql
      - /docker/onlyoffice/fonts:/usr/share/fonts

And I can successfully access the web interface, and I saw the instructions to start the examples:
sudo docker exec 03610350a9a6 sudo supervisorctl start ds:example
or
sudo docker exec 03610350a9a6 sudo sed 's,autostart=false,autostart=true,' -i /etc/supervisor/conf.d/ds-example.conf

I run those commands and they work. So from that example, I assume the correct way to create my own services is to create my own file with my own content in that directory.

However, the biggest thing I do not understand is how to make that service run permanently. As an example, lets say I just want to use the example permanently. (Only as an example)

  • I cannot simple do as the example says, as that will be lost upon upgrading the container.
  • I tried mapping the /etc/supervisor/conf.d folder to a local folder, putting my examples in it, and setting autostart=true. Upon restarting the container, nothing happened, and the logs seem to indicate it found no services to start. Even though I confirmed the files are in the correct location inside the container.

So what is the intended way to actually use this container?

Thanks!!

Host Operating System:
Linux EXAMPLE 6.11.10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1 (2024-11-23) x86_64 GNU/Linux
Docker version 26.1.5+dfsg1, build a72d7cd

Originally created by @1n5aN1aC on GitHub (Dec 21, 2024). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/784 Not exactly a bug, but probably a lack of understanding, and unable to find direction in the documentation. I wished to start with something very similar to the built-in example, (ds:example) so I started the docker container using docker-compose: ``` onlyoffice: container_name: onlyoffice image: onlyoffice/documentserver restart: always ports: - "1005:80" environment: JWT_SECRET: example_jwt_secret volumes: - /etc/localtime:/etc/localtime:ro - /docker/onlyoffice/files:/var/lib/onlyoffice - /docker/onlyoffice/db:/var/lib/postgresql - /docker/onlyoffice/fonts:/usr/share/fonts ``` And I can successfully access the web interface, and I saw the instructions to start the examples: `sudo docker exec 03610350a9a6 sudo supervisorctl start ds:example` or `sudo docker exec 03610350a9a6 sudo sed 's,autostart=false,autostart=true,' -i /etc/supervisor/conf.d/ds-example.conf` I run those commands and they work. So from that example, I assume the correct way to create my own services is to create my own file with my own content in that directory. However, the biggest thing I do not understand is how to make that service run permanently. As an example, lets say I just want to use the example permanently. (Only as an example) - I cannot simple do as the example says, as that will be lost upon upgrading the container. - I tried mapping the /etc/supervisor/conf.d folder to a local folder, putting my examples in it, and setting autostart=true. Upon restarting the container, nothing happened, and the logs seem to indicate it found no services to start. Even though I confirmed the files are in the correct location inside the container. So what is the intended way to actually use this container? Thanks!! **Host Operating System:** Linux EXAMPLE 6.11.10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1 (2024-11-23) x86_64 GNU/Linux Docker version 26.1.5+dfsg1, build a72d7cd
kerem 2026-02-26 10:32:06 +03:00
Author
Owner

@igwyd commented on GitHub (Dec 26, 2024):

Hello, that's because our application and services are configured to run in container when create image. I don’t know the details, but I guess that in your case you need to build your own container, for example, based on ours and configure your service. We will put the label "need help" because the question is beyond the scope of documentserver.

<!-- gh-comment-id:2562289445 --> @igwyd commented on GitHub (Dec 26, 2024): Hello, that's because our application and services are configured to run in container when create image. I don’t know the details, but I guess that in your case you need to build your own container, for example, based on ours and configure your service. We will put the label "need help" because the question is beyond the scope of documentserver.
Author
Owner

@1n5aN1aC commented on GitHub (Dec 26, 2024):

Hmm, alright.

So am I correct in understanding then that this container has no official way of running a specified service permanently? The user is expected to build their own container from the available sources and make the desired modifications at that level?

<!-- gh-comment-id:2563031026 --> @1n5aN1aC commented on GitHub (Dec 26, 2024): Hmm, alright. So am I correct in understanding then that this container has no official way of running a specified service permanently? The user is expected to build their own container from the available sources and make the desired modifications at that level?
Author
Owner

@igwyd commented on GitHub (Dec 27, 2024):

Yes, this container has way to run only own services, not custom.

The user is expected to build their own container from the available sources and make the desired modifications at that level?

You can create your app as you wish. It could be based on this container, a separeted container with an application and connect via network, not container etc . There could be many optios.

<!-- gh-comment-id:2563375557 --> @igwyd commented on GitHub (Dec 27, 2024): Yes, this container has way to run only own services, not custom. > The user is expected to build their own container from the available sources and make the desired modifications at that level? You can create your app as you wish. It could be based on this container, a separeted container with an application and connect via network, not container etc . There could be many optios.
Author
Owner

@1n5aN1aC commented on GitHub (Jan 4, 2025):

Thank you for explaining.

<!-- gh-comment-id:2571405129 --> @1n5aN1aC commented on GitHub (Jan 4, 2025): Thank you for explaining.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#359
No description provided.