podman: podman compose it not working on some projects on macOS
Issue Description
I tried to run https://github.com/change-metrics/monocle#installation using podman compose
but Iβm not able to make it work
issue is around volumes
There is a :z flag preventing the startup but even removing the π flag we have then the error
monocle-elastic-1 | ElasticsearchException[failed to bind service]; nested: AccessDeniedException[/usr/share/elasticsearch/data/nodes];
monocle-elastic-1 | Likely root cause: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/nodes
monocle-elastic-1 | at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90)
monocle-elastic-1 | at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
monocle-elastic-1 | at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
monocle-elastic-1 | at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:397)
monocle-elastic-1 | at java.base/java.nio.file.Files.createDirectory(Files.java:700)
monocle-elastic-1 | at java.base/java.nio.file.Files.createAndCheckIsDirectory(Files.java:807)
monocle-elastic-1 | at java.base/java.nio.file.Files.createDirectories(Files.java:793)
monocle-elastic-1 | at org.elasticsearch.env.NodeEnvironment.lambda$new$0(NodeEnvironment.java:300)
monocle-elastic-1 | at org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:224)
monocle-elastic-1 | at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:298)
monocle-elastic-1 | at org.elasticsearch.node.Node.<init>(Node.java:429)
monocle-elastic-1 | at org.elasticsearch.node.Node.<init>(Node.java:309)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:234)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160)
monocle-elastic-1 | at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77)
monocle-elastic-1 | at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112)
monocle-elastic-1 | at org.elasticsearch.cli.Command.main(Command.java:77)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125)
monocle-elastic-1 | at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80)
monocle-elastic-1 | For complete error details, refer to the log at /usr/share/elasticsearch/logs/docker-cluster.log
in the elastic search container
Steps to reproduce the issue
Steps to reproduce the issue
- git clone https://github.com/change-metrics/monocle
- cd monocole
- echo CRAWLERS_API_KEY=$(uuidgen) > .secrets
- podman compose up
Describe the results you received
failure
~/git/containers/podman/bin/darwin/podman compose up
>>>> Executing external compose provider "/opt/homebrew/bin/docker-compose". Please refer to the documentation for details. <<<<
[+] Running 3/0
β Container monocle-elastic-1 Recreated 0.0s
β Container monocle-api-1 Recreated 0.0s
β Container monocle-crawler-1 Recreated 0.0s
Attaching to monocle-api-1, monocle-crawler-1, monocle-elastic-1
Error response from daemon: lsetxattr /Users/benoitf/git/change-metrics/monocle/data: operation not supported
Error: executing /opt/homebrew/bin/docker-compose up: exit status 1
volumes are using π suffix and it doesnβt work
volumes:
- "./etc:/etc/monocle:z"
Describe the results you expected
should work
podman info output
If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
About this issue
- Original URL
- State: open
- Created 10 months ago
- Comments: 25 (17 by maintainers)
@rhatdan @ashley-cui @n1hility WDYT? I think this may help resolve some issues wrt. volume mounts on qemu+plan9