OliveTin EZ-Start: The Next Generation. Deploy OliveTin-for-Channels from the Command Line without the Need for Portainer to be Installed in Advance!

Playground
,
#44

This is really embarrassing at this point.

Did that and got this

latest: Pulling from bnhf/olivetin

Digest: sha256:930c5bd00dddae5edc684548d19a245d16c5883331b8ded5cdaaa63d96772ffa

Status: Image is up to date for bnhf/olivetin:latest

5519549f2234edcab90fe8ca11cb44e0519f58f3743efa66ae243caed8f18f7f

and this

Standard Output

Portainer container creation failed

Standard Error

+ [[ -z '' ]]
+ portainerHost=127.0.0.1
+ portainerAdminPassword=[Redacted]
+ [[ 14 -lt 12 ]]
++ htpasswd -nbB admin [Redacted]
++ cut -d : -f 2
+ hashedPassword='$2y$05$7HEfEvFQ4x1hTXreq.ARg.h7e8wu0gEagRJp.k4tsnke2OK723gJK'
+ portainerHttpPort=9000
+ portainerHttpsPort=9443
+ docker run -d -p 9000:9000 -p 9443:9443 --name portainer --restart always --pull always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest --admin-password '$2y$05$7HEfEvFQ4x1hTXreq.ARg.h7e8wu0gEagRJp.k4tsnke2OK723gJK'
latest: Pulling from portainer/portainer-ce
Digest: sha256:224a378fbc5ae579dc9d570c5ca2e5e981a4a003c8d7c2c5b5e482af97c2f87c
Status: Image is up to date for portainer/portainer-ce:latest
docker: Error response from daemon: Conflict. The container name "/portainer" is already in use by container "b5459aea0ab1345b4bb8d7354aaf76777dc7f2c37c94073ecc9b6f8e8ced6a2d". You have to remove (or rename) that container to be able to reuse that name.

Run 'docker run --help' for more information
+ echo 'Portainer container creation failed'
+ exit 0
1 Like
#45

Did you run the Install Portainer on your Docker Host Action multiple times?

#46

Just once with the incorrect ip address. Then once when I tried to fix it.

#47

I didn't realize you'd gone past the first step with the incorrect IP address. Run all 7 commands above again from Terminal, so you can start fresh, and step through everything again.

Accuracy is what's important not speed, so double check what you're doing before executing each step.

#48

I entered the ezstart docker run command (correct ip) in terminal and got this:

latest: Pulling from bnhf/olivetin

Digest: sha256:930c5bd00dddae5edc684548d19a245d16c5883331b8ded5cdaaa63d96772ffa

Status: Image is up to date for bnhf/olivetin:latest

docker: Error response from daemon: Conflict. The container name "/olivetin-ezstart" is already in use by container "5519549f2234edcab90fe8ca11cb44e0519f58f3743efa66ae243caed8f18f7f". You have to remove (or rename) that container to be able to reuse that name.

Should I just delete the container from docker?

#49

@kleywelsh Run the 7 commands above in Terminal, and then run:

docker ps

and post the entire output here. Copy and paste both your commands, and the output so I can see everything. It should be just one big copy-and-paste.

#50

layla@Kleys-Mac-mini ~ % docker stop olivetin-ezstart
docker rm olivetin-ezstart
docker rmi bnhf/olivetin:latest
docker stop portainer
docker rm portainer
docker volume rm portainer_data
docker rmi portainer/portainer-ce:latest
olivetin-ezstart
olivetin-ezstart
Untagged: bnhf/olivetin:latest
Deleted: sha256:930c5bd00dddae5edc684548d19a245d16c5883331b8ded5cdaaa63d96772ffa
portainer
portainer
portainer_data
Untagged: portainer/portainer-ce:latest
Deleted: sha256:224a378fbc5ae579dc9d570c5ca2e5e981a4a003c8d7c2c5b5e482af97c2f87c
layla@Kleys-Mac-mini ~ % docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

#51

It appears it worked, but it looks like you pasted all 7 commands in at once. The idea was to run them one at a time.

OK, so you've deleted everything, and we can see from docker ps there are no containers running. You should be able to proceed -- it's important to understand though that the first couple of steps can only be run once, or you need to delete everything and start again.

#52

Thank you so much. I can't thank you enough for your patience. It looks like you are the developer. Any place to donate?

#53

No problem. It is my project. I don't accept donations, but thanks for the offer. :slight_smile:

#54

I'm hesitant to post again, but I did everything I was supposed (even entered the EZstart docker run command line by line) and this is what I got when I went to Install Portainer on your Docker. I think I am done for tonight and if you are done with this, I get it.

Install Portainer on your Docker Host

Standard Output

7f7ec24062b9fe4262af3375d9dc9b203ecf2cf29a8b8dc1e0d9e6e66f5b3f01
Portainer container created successfully

Portainer token creation and environment initialization failed...

Standard Error

+ [[ -z '' ]]
+ portainerHost=127.0.0.1
+ portainerAdminPassword=[Redacted]
+ [[ 13 -lt 12 ]]
++ htpasswd -nbB admin [Redacted]
++ cut -d : -f 2
+ hashedPassword='$2y$05$dpe1sqARcjtvDT755j.fNeH.E8.JdWas4pAgMsGsyjMGpESxGLBKS'
+ portainerHttpPort=9000
+ portainerHttpsPort=9443
+ docker run -d -p 9000:9000 -p 9443:9443 --name portainer --restart always --pull always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest --admin-password '$2y$05$dpe1sqARcjtvDT755j.fNeH.E8.JdWas4pAgMsGsyjMGpESxGLBKS'
latest: Pulling from portainer/portainer-ce
4f4fb700ef54: Pulling fs layer
63c930229559: Pulling fs layer
d3b1c06ebf8c: Pulling fs layer
354e5ce52559: Pulling fs layer
8d59d73e40c6: Pulling fs layer
e811f1a0940a: Pulling fs layer
60aae008ce70: Pulling fs layer
605b6f3b7115: Pulling fs layer
24f6f070c2a7: Pulling fs layer
71eec8d28aa8: Pulling fs layer
4f4fb700ef54: Download complete
71eec8d28aa8: Download complete
63c930229559: Download complete
d3b1c06ebf8c: Download complete
63c930229559: Pull complete
d3b1c06ebf8c: Pull complete
605b6f3b7115: Download complete
e811f1a0940a: Download complete
60aae008ce70: Download complete
354e5ce52559: Download complete
354e5ce52559: Pull complete
24f6f070c2a7: Download complete
8d59d73e40c6: Download complete
8d59d73e40c6: Pull complete
605b6f3b7115: Pull complete
e811f1a0940a: Pull complete
24f6f070c2a7: Pull complete
4f4fb700ef54: Pull complete
71eec8d28aa8: Pull complete
60aae008ce70: Pull complete
Digest: sha256:224a378fbc5ae579dc9d570c5ca2e5e981a4a003c8d7c2c5b5e482af97c2f87c
Status: Downloaded newer image for portainer/portainer-ce:latest
+ echo 'Portainer container created successfully'
+ sleep 2
++ curl -s -X POST http://127.0.0.1:9000/api/auth -H 'Content-Type: application/json' -d '{"Username":"admin", "Password":"[Redacted]"}'
++ jq -r .jwt
+ jsonWebToken=
++ curl -s -X POST http://127.0.0.1:9000/api/users/1/tokens -H 'Authorization: Bearer ' -H 'Content-Type: application/json' -d '{"password": "[Redacted]", "description": "olivetin"}'
++ jq -r .rawAPIKey
+ portainerToken=
++ curl -s -X POST http://127.0.0.1:9000/api/endpoints -H 'Authorization: Bearer ' -F Name=local -F EndpointCreationType=1
++ jq -r .Id
+ portainerEnv=
+ [[ -n '' ]]
+ echo -e '\nPortainer token creation and environment initialization failed...'
#55

I'm packing it in too...

FYI, the EZ-Start Docker run command cannot be run line-by-line. When you see a command that has backslashes at the end of each line, that indicates a continuation, and a command like that is designed to (and must) be run complete.

This form is for commands to be run one-by-one:

docker stop olivetin-ezstart
docker rm olivetin-ezstart
docker rmi bnhf/olivetin:latest
docker stop portainer
docker rm portainer
docker volume rm portainer_data
docker rmi portainer/portainer-ce:latest

This form is for a multi-line command, that needs to be run as a unit:

docker run -d --name olivetin-ezstart \
--pull always \
-p 1338:1337 \
-e EZ_START=-ezstart \
-e CHANNELS_DVR=x.x.x.x:8089 \
-e TZ=$(readlink /etc/localtime) \
-v /config \
-v /var/run/docker.sock:/var/run/docker.sock \
bnhf/olivetin:latest

If you're comfortable with the concept, we could do a Chrome Remote Desktop session tomorrow, or over the weekend and I can get you up-and-running. PM me if you'd like to do that. Otherwise we can keep trying here soon.

#56

This actually escaped my notice with the other issues we were dealing with yesterday. :frowning: One of the concepts to understand with Docker is that it's a lightweight virtualization environment, which means that each container is a type of virtual machine.

This is important because when you use an IP address like 127.0.0.1 or a hostname like local localhost from within a container you're referring to that container, not to your Docker host computer (which in this case is your Mac Mini). So, you need to use the LAN IP of your Mac Mini in your Docker EZ-Start command.

So, go ahead and run those 7 commands again from Terminal, and then run the EZ-Start command (as a block). But this time be sure to use LAN IP of your Mac Mini. If you don't know it, execute this command from Terminal to get it:

ipconfig getifaddr en0

This assumes your Mini is connected with Ethernet.

#57

Working on it. Had not been using Ethernet but am now.

#58

I just ran Watchtower to update my Portainer stacks and Watchtower found an update for OliveTin. The Watchtower log showed an error updating OliveTin. The error is:

Failed to deploy a stack: compose up operation failed: Error response from daemon: error while creating mount source path '/host_mnt/Volumes/DVRVault/DVR': mkdir /host_mnt/Volumes/DVRVault: file exists

I'm not sure what this error is telling me. Portainer, Watchtower, ADBTuner and OliveTin were all installed via OliveTin EZ-Start. Everything had been working well and Watchtower updated OliveTin a couple of times in the past without error. I deleted the OliveTin stack and reinstalled into Portainer using the OliveTin EZ-Start with 2 Environmental Vars. The initial install with 2 vars worked but when I stopped the stack and and tried updating it with the vars generated by OliveTin - Variables Generator/Tester Action the update again failed.

CDVR and Docker/Portainer are running on a Mac Mini M2. CDVR data is stored on an external drive (DVRVault) attached to the Mac mini. CDVR is not installed in Docker/Portainer.

A copy of my Environmental Vars:

TAG=latest
DOMAIN=
HOST_PORT=1337
CHANNELS_DVR_HOST=192.168.0.5
CHANNELS_DVR_PORT=8089
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=*********@gmail.com
ALERT_EMAIL_PASS=***********
ALERT_EMAIL_TO=**********@gmail.com
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Central
HOST_DIR=/Users/danielmiller
DVR_SHARE=/Volumes/DVRVault/DVR
LOGS_SHARE=/Users/danielmiller/Library/Application Support/ChannelsDVR
TUBEARCHIVIST_SHARE=/Volumes/DVRVault/DVR
DVR2_SHARE=
LOGS2_SHARE=
TUBEARCHIVIST2_SHARE=
DVR3_SHARE=
LOGS3_SHARE=
TUBEARCHIVIST3_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=ptr_*******************
PORTAINER_HOST=192.168.0.5
PORTAINER_PORT=9443
PORTAINER_ENV=2
PERSISTENT_LOGS=false

Any ideas would be welcome.

#59

I haven't seen that error before, though I wonder if this has anything to do with it being an external drive. You might want to check Docker Desktop to be sure /Volumes is still showing as a writable location, under Settings - Resources - File Sharing - Virtual file shares.

Since you have your set of env vars, you don't really need to ever go through the EZ-Start process again. You can just go into Portainer and find the olivetin stack. Then, go into the editor for that stack, and make sure you have the latest Docker Compose for OliveTin, followed by adding your env vars into the area of the editor labelled Environment variables in Advanced mode. Then click Update the stack.

So, in short, make sure all is well with Docker being able to access your external drive. And then, check the olivetin stack in Portainer to be sure it's up-to-date and is using your specific set of env vars.

#60

Working now...

Thanks for the suggestion. As it happens I had a Mac OS update scheduled to be installed tonight so I thought I might as well install it now and see if anything else breaks. After installing the Mac OS update I checked Docker Desktop and saw an update was waiting there also. When I clicked the Docker update button I received an error msg and a button to fix the error. I clicked the fix button and Docker Desktop updated. I checked to make sure /Volumes was a writable location and it was. I thought I would try one more time to update the olivetin stack from Portainer with the full set of env vars. The stack updated and is running now. I ran the OliveTin Post-Install Healthcheck with no errors.

In short I have no idea why the Watchtower update failed or what changed in Docker. I ran the Mac OS update and the Docker update and that seems to have fixed the issue. Wish I had a better answer for anyone experiencing the same issues in the future.

Thanks to @bnhf for creating a great collection of tools and for all of the support provided here in the community forums.

1 Like
#61

EDIT: About an hour after the posting below, I went to the container area of Docker and clicked on the Portainer Port 9000 link and the Portainer web page opened. Onward through the fog....

===========

Got the following after the Portainer install:

Portainer container created successfully

Portainer token creation and environment initialization failed

Olive Tin and Project 1 Click seems to be working. Health check pretty good but says:

...
PORTAINER_HOST=
PORTAINER_PORT=
PORTAINER_ENV=
....

ls: cannot access '/mnt/nnn.nnn.n.nnn-': No such file or directory
error: no such object: olivetin
ls: cannot access '/mnt/nnn.nnn.n.nnn-_logs': No such file or directory

I tried to get this working about a year ago and gave up. Today I did a fresh install, but suspect I'm missing a few key settings. Thanks for any help with the next steps.

1 Like
#62

Go ahead and post the complete output from the OliveTin-for-Channels Post Install Healthcheck, and let's see where you're at...

#64

After I use the Olive Tin Environment Variables tool to fill in some blanks I will do that.