Containers don't work with Podman instead of Docker
See original GitHub issueI personally prefer using https://podman.io instead of Docker (because containers dont’ run as root, on the host; although you can still be root inside the container…), and when I tried that with this project (FYI they have a podman-compose
which, in my experience, is reasonably compatible with docker-compose
) but I’ve noticed that the images of this project don’t yet work with Podman instead of Docker. The web container for example failed with the error below (I hadn’t even checked the others.)
The short-term workaround is, of course, to just use Docker instead of Podman for now, but I thought I’d at least just let you know about this by filing this issue here.
Glancing over this project, I’ve noticed open PRs #192 and #126, it’s possible they help with this.
@saghul more of an FYI
[s6-init] making user provided files available at /var/run/s6/etc...
[s6-init] ensuring user provided files have correct perms...
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-set-timezone: executing...
[cont-init.d] 01-set-timezone: exited 0.
[cont-init.d] 10-config: executing...
mkdir: cannot create directory '/config/nginx': Permission denied
mkdir: cannot create directory '/config/keys': Permission denied
generating self-signed keys in /config/keys, you can replace these with your own keys if required
Generating a RSA private key
........................++++
....................................................................................................++++
writing new private key to '/config/keys/cert.key'
req: Can't open "/config/keys/cert.key" for writing, No such file or directory
Can't open /config/nginx/dhparams.pem for writing, No such file or directory
140389928026176:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:74:fopen('/config/nginx/dhparams.pem','w')
140389928026176:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:81:
cp: cannot create regular file '/config/nginx/nginx.conf': No such file or directory
/var/run/s6/etc/cont-init.d/10-config: line 44: /config/nginx/meet.conf: No such file or directory
/var/run/s6/etc/cont-init.d/10-config: line 48: /config/nginx/ssl.conf: No such file or directory
/var/run/s6/etc/cont-init.d/10-config: line 52: /config/nginx/site-confs/default: No such file or directory
cp: cannot create regular file '/config/config.js': Permission denied
sed: can't read /config/config.js: No such file or directory
cp: cannot create regular file '/config/interface_config.js': Permission denied
sed: can't read /config/interface_config.js: No such file or directory
[cont-init.d] 10-config: exited 2.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:17 (9 by maintainers)
Top GitHub Comments
Just a heads up I created a full guide for this as I was tired of not finding good information: http://tendie.haus/how-to-setup-a-basic-jitsi-instance-with-podman/
Currently I am creating files to create podman images in order to later on run the containers with the systemd.
But when I run a prosody container, I get the following errors
var/run/s6/etc/cont-init.d/10-config: line 4: /usr/bin/tpl: Permission denied ... /var/run/s6/etc/cont-init.d/10-config: line 30: /usr/bin/tpl: Permission denied /var/run/s6/etc/cont-init.d/10-config: line 31: /usr/bin/tpl: Permission denied
What could be the reason for the Permission denied ?