-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- ./setup.sh
- Do you want to start build process
ERRO[0000] reading system config "/home/vaultwarden/.config/containers/containers.conf": decode configuration /home/vaultwarden/.config/containers/containers.conf: toml: line 177 (last key "containers.log_driver"): Key 'containers.log_driver' has already been defined.
Expected behavior
presumably the build should finish and then offer to launch the image.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: CentOS 8 -> springdale 8, not CentOS Stream
Output from setup command:
Failed to look up user 10502: No such process
A dependency job for user@10502.service failed. See 'journalctl -xe' for details.
Do you want to start build process (y|n)
Enter your answer y
Executed Command :
sudo su - **vaultwarden** -c podman build -t centos-vaultwarden:latest --build-arg admpass=0JxByyPKOCowrRQx --build-arg OS=CentOS --build-arg HTTPS=443 -v /home/vaultwarden/.persistent_storage/vaultwarden:/var/lib/vaultwarden:Z -f /home/vaultwarden/.persistent_storage/project/Dockerfile
ERRO[0000] reading system config "/home/vaultwarden/.config/containers/containers.conf": decode configuration /home/vaultwarden/.config/containers/containers.conf: toml: line 177 (last key "containers.log_driver"): Key 'containers.log_driver' has already been defined.
Something goes wrong during build operation centos-vaultwarden:latest
[root@sal001675 yum.repos.d]# grep -C3 log_driver "/home/vaultwarden/.config/containers/containers.conf"
# Logging driver for the container. Available options: k8s-file and journald.
#
#log_driver = "k8s-file"
log_driver = "journald"
##log_driver = "k8s-file"
log_driver = "journald"
# Maximum size allowed for the container log file. Negative numbers indicate
# that no size limit is imposed. If positive, it must be >= 8192 to match or
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working