Permissions Problem

[usamitysam]

Hi,

I'm having permission problems when attempting to launch via signal-cli via docker demon on Ubuntu 18.04. I'm trying the docker method to avoid the library problems with glibc. Any help would be appreciated. I added a little extra white space to make the info below a bit more readable.

Interestingly, the directory /home/MYUSER/.local/share/signal-cli/ is created but just not signal-cli.log

-- Thanks

MYUSER@MYSERVER:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

MYUSER@MYSERVER:~$ docker run -d --name signal-cli -e PUID=1000 -e PGID=1000 --publish 7583:7583 --volume /home/MYUSER/.local/share/signal-cli:/var/lib/signal-cli --tmpfs /tmp:exec registry.gitlab.com/packaging/signal-cli/signal-cli-native:latest daemon --tcp 0.0.0.0:7583 --log-file /home/MYUSER/.local/share/signal-cli/signal-cli.log

ecc46c195353783407310b2adeb93f103f7463c4434e81a2f86ea8252883062a

MYUSER@MYSERVER:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ecc46c195353 registry.gitlab.com/packaging/signal-cli/signal-cli-native:latest "/usr/bin/signal-cli…" 3 seconds ago Exited (1) 2 seconds ago signal-cli

MYUSER@MYSERVER:~$ docker logs signal-cli
01:28:48,465 |-INFO in ch.qos.logback.classic.LoggerContext[default] - This is logback-classic version 1.4.11
01:28:48,465 |-INFO in ch.qos.logback.classic.util.ContextInitializer@538fcf9e - Here is a list of configurators discovered as a service, by rank:
01:28:48,465 |-INFO in ch.qos.logback.classic.util.ContextInitializer@538fcf9e - org.asamk.signal.logging.LogConfigurator
01:28:48,465 |-INFO in ch.qos.logback.classic.util.ContextInitializer@538fcf9e - They will be invoked in order until ExecutionStatus.DO_NOT_INVOKE_NEXT_IF_ANY is returned.
01:28:48,465 |-INFO in ch.qos.logback.classic.util.ContextInitializer@538fcf9e - Constructed configurator of type class org.asamk.signal.logging.LogConfigurator
01:28:48,472 |-INFO in org.asamk.signal.logging.LogConfigurator$3[file] - File property is set to [/home/MYUSER/.local/share/signal-cli/signal-cli.log]
01:28:48,472 |-ERROR in org.asamk.signal.logging.LogConfigurator$3[file] - Failed to create parent directories for [/home/MYUSER/.local/share/signal-cli/signal-cli.log]
01:28:48,476 |-ERROR in org.asamk.signal.logging.LogConfigurator$3[file] - openFile(/home/MYUSER/.local/share/signal-cli/signal-cli.log,true) call failed. java.io.FileNotFoundException: /home/MYUSER/.local/share/signal-cli/signal-cli.log (No such file or directory)
at java.io.FileNotFoundException: /home/MYUSER/.local/share/signal-cli/signal-cli.log (No such file or directory)
at at [email protected]/java.io.FileOutputStream.open0(FileOutputStream.java)
at at [email protected]/java.io.FileOutputStream.open(FileOutputStream.java:293)
at at [email protected]/java.io.FileOutputStream.(FileOutputStream.java:235)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:26)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:206)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:126)
at at org.asamk.signal.logging.LogConfigurator$3.(LogConfigurator.java:98)
at at org.asamk.signal.logging.LogConfigurator.createLoggingFileAppender(LogConfigurator.java:93)
at at org.asamk.signal.logging.LogConfigurator.configure(LogConfigurator.java:72)
at at ch.qos.logback.classic.util.ContextInitializer.invokeConfigure(ContextInitializer.java:122)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:87)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:65)
at at ch.qos.logback.classic.spi.LogbackServiceProvider.initializeLoggerContext(LogbackServiceProvider.java:52)
at at ch.qos.logback.classic.spi.LogbackServiceProvider.initialize(LogbackServiceProvider.java:41)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:195)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:182)
at at org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:490)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:476)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:425)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:451)
at at org.asamk.signal.App.(App.java:50)
at at org.asamk.signal.Main.main(Main.java:55)
01:28:48,476 |-INFO in ch.qos.logback.classic.util.ContextInitializer@538fcf9e - org.asamk.signal.logging.LogConfigurator.configure() call lasted 11 milliseconds. ExecutionStatus=DO_NOT_INVOKE_NEXT_IF_ANY

usage: signal-cli daemon [-h] [--dbus] [--dbus-system] [--socket [SOCKET]]
[--tcp [TCP]] [--http [HTTP]] [--no-receive-stdout]
[--receive-mode {on-start,on-connection,manual}]
[--ignore-attachments] [--ignore-stories]
[--send-read-receipts]
signal-cli: error: unrecognized arguments: '--log-file'

[usamitysam]

Decided to try Pushover app instead. My concern above is less critical now.