Vaultwarden - postgres:'docker login': denied: requested access to the resource is denied - closed

Team,

I tried to install vaultwarden with this issue:

Blockquote
postgres_upgrade Warning pull access denied for ix-postgres, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied

and

Blockquote
(ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: Network ix-vaultwarden_default Creating
Network ix-vaultwarden_default Created
Container ix-vaultwarden-postgres_upgrade-1 Creating
level=warning msg=“config uid, gid and mode are not supported, they will be ignored”

I setup a passsword before during the setup.
Any idea or where is my setup issue?

Should I delete the password and reset after the installation procedure?

Thanks
Neuro

Did you use iXVolume or hostpath for storage?
In both cases did you check the “automatic permission” checkbox so that postgress has the right permission?

Hi Lars,

I selected hostpath and checked the box “automatic permission”.

Now I have:

Blockquote
56 - Failed ‘up’ action for ‘vaultwarden’ app: permissions Pulling

there was a post similar to yours not long ago

maybe their solution can help you.

1 Like

…wasn’t my solution

Blockquote
ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: permissions Pulling

dirctly at the beginning:

Blockquote
(ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: permissions Pulling
bc0965b23a04 Pulling fs layer
dcccf87d013d Pulling fs layer
acee09de1c5d Pulling fs layer
a576ef79af7e Pulling fs layer
a576ef79af7e Waiting
acee09de1c5d Downloading [>…

When I installed as recommanded - without host path - deployments are successfull…

Hmmm… Every post on the forum describing problems with vaultwarden were postgress permission related, but reading your first post again it seems, that the app installer has problems to reach the repository to pulll files.
When was the last time you refreshed the apps catalogue? I looked on github and it seems there were some changed made yesterday.

When I installed as recommanded - without host path - deployments are successfull…

I started this morning to install vw…

Ok that still hints back to a permission issue on your hostpath datasets.
I would propably try to delete you current vaultwarden datasets, create new ones and apply permissions for user 999 (netdata) manually. Postgress wants to run as user 999 and then try to install it fresh.
If that also doesn’t work im out if ideas. My knowledge of the buildin apps system is limited since i’m still using a scale-jail and portainer with my own docker-compose to deploy it.

1 Like

Does it mean to install portainer and then deploy vw??

vaultwarden is one of the few apps i’ve deployed where i manually used docker-compose up -d because i’m using a .env file and i don’t like portainers implementation of .env files. It still shows up in the portainer gui and has limited managability

it definitely has something to do with the HOST PATH, as I can get an error-free deployment with the recommended config

Error with selected HOST Path:

Blockquote
(ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: postgres Pulling
postgres_upgrade Warning pull access denied for ix-postgres, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied
Container ix-vaultwarden-postgres_upgrade-1 service “postgres_upgrade” didn’t complete successfully: exit 1

So, as @LarsR has been saying, it’s an issue with your postgres dataset permissions. Try creating a new dataset using the Generic preset, so it has posix permissions, don’t try manually adjusting permissions for now. Then install again using your new dataset as a host path, select enable ACL and automatic permissions.

1 Like

Thanks for reply.
I’ll do it and will give feedback soon.

Thx
Neuro

A permission step forward …but unfortunately not accomplished…

Blockquote
[2025/02/12 11:25:17] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: vaultwarden Pulling
c29f5b76f736 Already exists
00b74c3a8e0f Pulling fs layer
2941ad44fa1c Pulling fs layer
83805dacd5c4 Pulling fs layer
9ce20ffad878 Pulling fs layer
9ce20ffad878 Waiting
2941ad44fa1c Downloading [============================> ] 720B/1.263kB
2941ad44fa1c Downloading [==================================================>] 1.263kB/1.263kB
2941ad44fa1c Verifying Checksum
2941ad44fa1c Download complete
83805dacd5c4 Downloading [> ] 179.8kB/17.77MB
00b74c3a8e0f Downloading [> ] 152.2kB/14.85MB
83805dacd5c4 Downloading [==> ] 727.3kB/17.77MB
83805dacd5c4 Downloading [===> ] 1.268MB/17.77MB
.
.
.
Network ix-vaultwarden_default Creating
Network ix-vaultwarden_default Created
Container ix-vaultwarden-postgres_upgrade-1 Creating
time=“2025-02-12T11:25:14+01:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-vaultwarden-postgres_upgrade-1 Created
Container ix-vaultwarden-postgres-1 Creating
Container ix-vaultwarden-postgres-1 Created
Container ix-vaultwarden-vaultwarden-1 Creating
Container ix-vaultwarden-vaultwarden-1 Created
Container ix-vaultwarden-postgres_upgrade-1 Starting
Container ix-vaultwarden-postgres_upgrade-1 Started
Container ix-vaultwarden-postgres_upgrade-1 Waiting
Container ix-vaultwarden-postgres_upgrade-1 Exited
Container ix-vaultwarden-postgres-1 Starting
Container ix-vaultwarden-postgres-1 Started
Container ix-vaultwarden-postgres-1 Waiting
Container ix-vaultwarden-postgres-1 Error
dependency failed to start: container ix-vaultwarden-postgres-1 is unhealthy

Ok, i will stopp further investigation.

Blockquote
[2025/02/12 12:09:22] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘vaultwarden’ app: Network ix-vaultwarden_default Creating
Network ix-vaultwarden_default Created
Container ix-vaultwarden-postgres_upgrade-1 Creating
time=“2025-02-12T12:09:19+01:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-vaultwarden-postgres_upgrade-1 Created
Container ix-vaultwarden-postgres-1 Creating
Container ix-vaultwarden-postgres-1 Created
Container ix-vaultwarden-vaultwarden-1 Creating
Container ix-vaultwarden-vaultwarden-1 Created
Container ix-vaultwarden-postgres_upgrade-1 Starting
Container ix-vaultwarden-postgres_upgrade-1 Started
Container ix-vaultwarden-postgres_upgrade-1 Waiting
Container ix-vaultwarden-postgres_upgrade-1 Exited
Container ix-vaultwarden-postgres-1 Starting
Container ix-vaultwarden-postgres-1 Started
Container ix-vaultwarden-postgres-1 Waiting
Container ix-vaultwarden-postgres-1 Error
dependency failed to start: container ix-vaultwarden-postgres-1 is unhealthy

I’m not able to fix this issue.

Thank you for your support.

Ok, troubleshooting doesn’t let me go that easily.

Procedure actually as described above by @LarsR and @DjP-iX

  • create a clean, untreated dataset

  • select exactly this dataset in the path selection, both for VW and for Postgres data

  • mark “Automatic permission”

…and suddenly the deployment was through…wonder why…it didn’t work before with exactly the same procedure…