I'm at a total loss here.. there's no reason that docker-compose file (or the docker-run command for that matter) should not work.
Did you get an error when the stack deployed, or did it deploy successfully?
I'm at a total loss here.. there's no reason that docker-compose file (or the docker-run command for that matter) should not work.
Did you get an error when the stack deployed, or did it deploy successfully?
I'm beginning to think something in his docker install is hosed. Can the OP create any other new containers without difficulty, or do they fail too?
I'm beginning to think something in his docker install is hosed. Can the OP create any other new containers without difficulty, or do they fail too?
I was wondering that myself a bit ago... but not really sure how that would happen.
Just seems odd you and I have both done this a couple different ways w/o issue, and he keeps getting permission denied
Maybe try to delete your local image and run the command again.
This is what I did:
1. created Grafana folder on the OS drive
2. gave permissions: dockeruser:users
3. Executed the docker compose file
4. container is created, but can’t be run.
5. no log error
I currently have Nextcloud and Netdata running in docker fine.
I tested this using @KM0201 compose file, first try it failed I had another container using 3000, tried changing the port but that also failed, so stopped the container using port 3000 and ran the compose again and this time it worked.
Interesting that changing the port would also fail. I didn't have 3000 in use so it worked first try
Alles anzeigenThis is what I did:
1. created Grafana folder on the OS drive
2. gave permissions: dockeruser:users
3. Executed the docker compose file
4. container is created, but can’t be run.
5. no log error
I currently have Nextcloud and Netdata running in docker fine.
Try installing a simple container, even if you don't intend to use it. linuxserver/airsonic is easy,,,, and see if it starts up OK. You can point it at blank directories just to test it
Interesting that changing the port would also fail.
I set port 4000 and I got couldn't connect and that was after it was showing as running after 2 mins
Alles anzeigenThis is what I did:
1. created Grafana folder on the OS drive
2. gave permissions: dockeruser:users
3. Executed the docker compose file
4. container is created, but can’t be run.
5. no log error
I currently have Nextcloud and Netdata running in docker fine.
1. & 2. Not sure why you did this, it's not referenced at all in the provided compose file. There are no Volume mappings defined in the compose file, so what is the purpose of the Grafana folder?
Also, ownership and permissions are not the same thing.
Without creating a Grafana folder, how are you make the data persistence ?
1. & 2. Not sure why you did this, it's not referenced at all in the provided compose file. There are no Volume mappings defined in the compose file, so what is the purpose of the Grafana folder?
Also, ownership and permissions are not the same thing.
I just caught that. That's gotta be part of the problem
Without creating a Grafana folder, how are you make the data persistence ?
It will all be mapped inside the container folder.
Try running just the compose file, no additions and see if it starts OK. It does take a second to start.
According to Grafana documentation, it’s recommended to create a volume.
Anyway, I’ll try it tonight without any volume or folder mapping.
https://grafana.com/docs/grafana/latest/installation/docker/
According to Grafana documentation, it’s recommended to create a volume.
Anyway, I’ll try it tonight without any volume or folder mapping.
https://grafana.com/docs/grafana/latest/installation/docker/
That's fine... but for now, try creating it w/o your volumes. I think that is part of the problem. Then try to add them in.
OP, your volumes definitely your problem (not sure why though)... I just tried mapping those directories to a couple volumes I created, and I'm getting the same permission denied error you are. I know beyond doubt I have permission on that directory.
Interesting.
I’ll try it out and let you guys know the result.
Just to try it out: chown -R 472:472 your grafana folder (if you bind mounted this folder) and try again.
I think 472 is Grafana userid.
Is this meant I need to create this user ?
No. Just try to chown the dir. No need to create a user. I
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!