-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitwarden_rs: ./run: line 81: /opt/bitwarden_rs: No such file or directory #4
Comments
That's so strange... This file is created during build so I don't understand how it wouldn't be there. Did you try to install the official community addon here and was it working ? The code is nearly the same. |
OK I'll try something... Could you please uninstall, manually update the repo, and try again to install? For info, I had linked the bitwarden build link with the addon version. It works on my config but it is the only difference in build instructions with the official addon (that was on v1.17 so causes sync issues with apps). I've reverted it tonhard encoded links. |
I reload the repo's reinstalled the add-on but still get the error:
i see that it is version 1.18.0 The official one is working. When I try yours first I turn of the original one. Hope yours will work with latest iOS version and the app. |
Trying something |
This is the full log file after I tried you other REPO link:
|
I really don't understand... Actually you were so fast to install the new repo that I did not have time to make the modif - so it is actually directly the official addon (forked by mww to install the v 1.17.0). However, I got a new idea. I saw that all files are in CRLF (windows line return) and not in LF (unix line return). It could cause some issues with scripts depending on the systems. As distribution, I'm using Home Assistant OS, and I see that you are on Debian, so it could be that system behavior is not identical. I've updated my own addon with that. Low probability it will work as the offical addon is also in CRLF. It is now uploaded so if you reload the repro it will install the version with LF. The last possibility would be for you to install mww's version here : https://github.com/mww/addon-bitwarden Otherwise, if both those options fail (my addon with LF), and mww version then I really don't see how to help. |
I tried MWW his repo. Same issue:
It can not be a problem I already have official Bitwarden_RS installed? The container name is different so would be a problem right? I guess I can't use it. :( |
This is the official Bitwarden_RS from HA itself:
|
Indeed the current addon works - what seems not to work is the ability to download files during creation of the container through the dockerfile. It is what failed on the nextcloud addon, and on my & mww's addons. And yes, as the container name is different you can have 2 different bitwarden addons on your system! It tested that in the past. Sorry but it seems to be an issue on your system then... Actually the most interesting test would be to uninstall the official addon and try to reinstall it ;-) If you have a snapshot you can always restore your current bitwarden system afterwards. If it works then I would try to understand but the code is near identical so there is no reason the offical addon would work and not the forks... |
All official Addons I can install without problem. That makes not logic that it will be a problem of my os system? |
I've corrected an error in the code. Could you try again? |
I did a reload and installed the Add-on. I used the repo: alexbelgium/hassio-addons
|
This is a output of portainer:
|
Thanks, and can you confirm that you have no error in your supervisor log when building the addon? Because I really don't understand why it doesn't seem to install the bitwarden layer... And my portainer image info is totally different here I can't find any of the dockerfile commands... Even the bash is not the same! I have bash in the script and here it is sh... I'll request help in the forum. |
Here supervisor log:
When I start the add-on is this the rest of the log:
|
Thanks for so much infos and tests. So supervisor is OK but I really don't understand the layout of your docker image in portainer. I'll request some help in the forum |
For info, the official addon will be updated soon. I've made a last update (removed labels that could interfere with build) but I'll stop searching unless I receive another idea by another dev. |
Reload repo. Install. Start. :( same issue... Will wait for new version. Maybe that one will work. |
I tried something. Saw a tutor to install something from docker-hub using Portainer.
The install went ok. I did http:// and give the random port: 49154 Bitwarden_RS version 2.14.0 Now figure out how to enable the ADMIN panel because get a message:
I think I have to login into the docker and change something over there But this was working without any problem..... |
Hi, nicely done! However, the fopina/bitwarden_rs is from May, and is based on the v1.15.0-1 according to docker hub. There should still be your issue with iOS app. The normal docker image is bitwardenrs/server:1.18.0 Actually the ADMIN_TOKEN is generated by a script in the hassio addon. You can do that manually : with portainer, you need to create in your docker image an Environement variable [ENV] named "ADMIN_TOKEN" that contains any random things that you want. Here is the official documention : https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-admin-page However, I saw that the maintainer is busy updating the official addon! He worked on it this morning but didn't publish it yet. I have aligned my code this morning with his changes (mainly, updating the base layer). You could still try to remove my repo, re-add it and install my bitwarden addon 1.18.0 but my hopes are low ;-) However the official addon should be updated in a couple days! |
I installed now the official: bitwardenrs/server
Also without any problem. Even the ADMIN_TOKEN part worked. This docker install via Portainer is not visible in HA... So no nice backup solution. |
You should update the official addon it has been updated to 0.7.0! |
haha... how ironic... Everything is working, include iOS App and auto-fill support.... |
Ahahah indeed how ironic! Glad it's working for you, and anyway I'm sure we both have gained a lot of knowledge trying to make it work! Regarding my addon the only reason I did mine is because Frenck did not update his own for a very long time. So there is no benefit of mine over the current official one ;) I'll however still keep it as i don't know how often the official one will be updated in the future! |
If yours is updated ill give it a try, then im sure it will updates sooner then the HA version. |
Hello All,
When I want start Bitwarden_RS I see this error message:
./run: line 81: /opt/bitwarden_rs: No such file or directory
RPI4 2GB
Home Assistant 2021.1.4
Installation Type | Home Assistant Supervised
Development | false
Supervisor | true
Docker | true
Virtual Environment | false
Python Version | 3.8.7
Operating System Family | Linux
Operating System Version | 5.4.79-v8+
CPU Architecture | aarch64
Timezone | Europe/Amsterdam
The text was updated successfully, but these errors were encountered: