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
Note:
Added the line: --security-opt apparmor=unconfined because apparmor is activated
Removed the lines below, because do not know what to fill in:
--memory {MEMORY}
--memory-swap {SWAP MEMORY}
The image is downloaded en installed. The image is running. But that's it. There are no logfiles in the container. Accessing the container does not work.
Setting the timezone fails because it says: container is starting docker exec 3cx timedatectl set-timezone {YOUR ZONE INFO} 943c560604bf********** is restarting, wait until the container is running,
Looks like the container is restarting (many times)
Do not know if this is a known issue?
The text was updated successfully, but these errors were encountered:
First of all I like the idea of running 3cx in a docker container. Thank for the great work. This is what I did:
Created a macvlan:
-d macvlan
--subnet 192.168.2.0/24
--gateway 192.168.2.254
-o parent=eno1 mv_eno1
Then, used the CLI line to create the container:
docker run
-d
--hostname mousik.my3cx.nl
--ip 192.168.2.1xx
--network mv_eno1
--restart unless-stopped
--security-opt apparmor=unconfined
-v 3cx_backup:/data/3cx/backup
-v 3cx_recordings:/data/3cx/recordings
-v 3cx_log:/data/3cx/log
-v /sys/fs/cgroup:/sys/fs/cgroup:ro
--cap-add SYS_ADMIN
--name 3cx
farfui/3cx:18.0.2.314
Note:
Added the line: --security-opt apparmor=unconfined because apparmor is activated
Removed the lines below, because do not know what to fill in:
--memory {MEMORY}
--memory-swap {SWAP MEMORY}
The image is downloaded en installed. The image is running. But that's it. There are no logfiles in the container. Accessing the container does not work.
Setting the timezone fails because it says: container is starting docker exec 3cx timedatectl set-timezone {YOUR ZONE INFO} 943c560604bf********** is restarting, wait until the container is running,
Looks like the container is restarting (many times)
Do not know if this is a known issue?
The text was updated successfully, but these errors were encountered: