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
name: NginXservices:
nginx:
image: nginx:alpineports:
- "0.0.0.0:80:80"volumes:
# - ./nginx/conf.d:/etc/nginx/conf.d # disabled becuase the container thinks `default.conf` is a directory
- ./nginx/html/:/usr/share/nginx/html/
- ./nginx/cert/:/etc/ssl/private/restart: always
My problem is when I try to access the NginX server I get a "403 Forbidden" (due to the /usr/share/nginx/html/ directory being empty) and a "404 Not Found" directly on the index page.
This issue is most likely related to #168 (comment) and basically means that we need figure out alternative solution to handling compose binary packaging.
BurmillaOS Version: (ros os version)
v2.0.2-rc2
Where are you running BurmillaOS? (docker-machine, AWS, GCE, baremetal, etc.)
Hyper V on Windows:
Which processor architecture you are using?
x86 64 (AMD Ryzen 7 5800H with Radeon Graphics)
Do you use some extra hardware? (GPU, etc)?
No
Which console you use (default, ubuntu, centos, etc..)
Default
Do you use some service(s) which are not enabled by default?
No
Have you installed some extra tools to console?
cifs-utils
,tree
Do you use some other customizations?
Does creating docker containers count?
Please share copy of your cloud-init (remember remove all sensitive data first)
I'm trying to run a simple NginX container but the bind mount inside the container is empty.
My direcory is set up like:
My
docker-compose.yml
is:My problem is when I try to access the NginX server I get a "403 Forbidden" (due to the
/usr/share/nginx/html/
directory being empty) and a "404 Not Found" directly on the index page.If I use
docker inspect
on the container I get:The significant problem here is that
/compose/nginx
is not my directory but/home/rancher/DOCKER/NginX
is.If I change the docker compsoe file to:
then everything works as expected.
TLDR:
./host/path:/container/path
) become/compose/host/path
instead of the actual path.If this is intended behaviour should the documentation be updated?
The text was updated successfully, but these errors were encountered: