You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I'd like to express my appreciation for the docker-mapproxy; it's a fantastic tool, and I'm grateful for the effort put into it.
I'm encountering an issue with running the container in Portainer CE 2.19.2, where my services from the .yaml files in the multi_mapproxy directory are not available after restarting the container. I am loading the mapproxy directory with the .yaml files at system startup from an external SSHFS storage.
Expected Behavior
When I restart the container, I expect all the services from the .yaml files in the mapproxy directory to be available, including mapproxy.yaml and seed.yaml.
Actual Behavior
After system reboot or restarting the container, none of the services are available, and even mapproxy.yaml and seed.yaml are not shown.
Workaround
Currently, I am working around this issue by:
Going to Stacks -> mapproxy.
On Stack details i click on Stop this stack
-> The Stack is stopping
Then i click on Start this stack
-> After these steps, all services become available. They will not, when i simply restart the container.
It would be more convenient if they loaded automatically at system start.
Steps to reproduce the issue
To replicate the issue I'm experiencing with docker-mapproxy in Portainer CE 2.19.2, please follow these steps:
Initial Setup:
Set up the multi_mapproxy directory to load at system startup with SSHFS. The following command is used in /etc/fstab to mount the directory:
Does the issue occur with a normal docker volume?, what are the logs when restarting the container. Does the restart delete your files or it overlays them obscuring them
What is the bug or the crash?
Firstly, I'd like to express my appreciation for the docker-mapproxy; it's a fantastic tool, and I'm grateful for the effort put into it.
I'm encountering an issue with running the container in Portainer CE 2.19.2, where my services from the .yaml files in the multi_mapproxy directory are not available after restarting the container. I am loading the mapproxy directory with the .yaml files at system startup from an external SSHFS storage.
Expected Behavior
When I restart the container, I expect all the services from the .yaml files in the mapproxy directory to be available, including mapproxy.yaml and seed.yaml.
Actual Behavior
After system reboot or restarting the container, none of the services are available, and even mapproxy.yaml and seed.yaml are not shown.
Workaround
Currently, I am working around this issue by:
Going to Stacks -> mapproxy.
On Stack details i click on
Stop this stack
-> The Stack is stopping
Then i click on
Start this stack
-> After these steps, all services become available. They will not, when i simply restart the container.
It would be more convenient if they loaded automatically at system start.
Steps to reproduce the issue
To replicate the issue I'm experiencing with docker-mapproxy in Portainer CE 2.19.2, please follow these steps:
Versions
MapProxy 1.16.0
Docker 24.0.7, build afdd53b
Portainer CE 2.19.2
host: Debian 6.1.55-1 x86_64
Additional context
This is my docker-compose i am using in portainer
version: '3.8'
services:
mapproxy:
image: kartoza/mapproxy
container_name: mapproxy
environment:
- PRODUCTION=True
- PROCESSES=4
- CHEAPER=1
- THREADS=10
- MAPPROXY_USER_ID=1000
- MAPPROXY_GROUP_ID=1000
- MULTI_MAPPROXY=True
- ALLOW_LISTING=True
- LOGGING=True
- HTTP_PROXY:http://x.x.x.x:3128
- HTTPS_PROXY=http://x.x.x.x:3128
# not opened on host, since its routed via Nginx Proxy Manager (npm-network)
# ports:
# - "8080:8080"
volumes:
- /mnt/[external_storage_sshfs]/multi_mapproxy:/multi_mapproxy
restart: always
networks:
- npm-network
networks:
npm-network:
external: true
The text was updated successfully, but these errors were encountered: