Closed trebestie closed 9 months ago
sethsandaru
commented
9 months ago hey @trebestie , thanks for using DocKing, sorries for the reply (not sure why I didn't receive any notification)
Do I get it right, that you deploy DocKing to your local network, and you can't access it?
Could you share more details? It would be really helpful, thanks
trebestie
commented
9 months ago Hi Seth, following the docker's way installation instructions I successfully deployed a Docking instance on a laptop. I got access to the console at 127.0.0.1 and played with templates. So I'm pretty sure there are no configuration issues. Then, I have a small server hosting some microservice each one of them inside a dedicated lxc container. I created a container (tried alpine/debian/ubuntu without any difference) and followed the same steps as installing on the laptop. The DocKing service starts, i access on the console page, but that I leave the password empty or that I write down the password after setting it in the .env file, i got an authentication failure. On the server side I'm unable to find any clue. The log file says nothing relevant. Differences between two systems are:
Many thanks for your help and for your very interesting project.
My regards
Il giorno mer 3 gen 2024 alle ore 07:11 Seth Phat @.***> ha scritto:
hey @trebestie https://github.com/trebestie , thanks for using DocKing, sorries for the reply (not sure why I didn't receive any notification)
Do I get it right, that you deploy DocKing to your local network, and you can't access it?
Could you share more details? It would be really helpful, thanks
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1874891804, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK23GXNK6R764TDZPYVLYMTY7RAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUHA4TCOBQGQ . You are receiving this because you were mentioned.Message ID: @.***>
-- Diego Depaoli
sethsandaru
commented
9 months ago @trebestie so you are running docking-dev image (on the repo) in the dedicated lxc container?
or do you build a custom image (follow this guide) with a proper .env file?
trebestie
commented
9 months ago I'm running docking-dev image with the compose file provided at https://docking.shipsaas.tech/getting-started/run-on-local/docker without changes.
Il giorno mer 3 gen 2024 alle ore 11:27 Seth Phat @.***> ha scritto:
@trebestie https://github.com/trebestie so you are running docking-dev image (on the repo) in the dedicated lxc container? or do you already have your custom version with a proper .env file?
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1875144872, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK276CY4GVOHVW5VXTVDYMUXBXAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGE2DIOBXGI . You are receiving this because you were mentioned.Message ID: @.***>
-- Diego Depaoli
sethsandaru
commented
9 months ago I see, so that's why you weren't able to access it. We have these 2 env variables that need to be updated when rolling live
https://github.com/shipsaas/docking/blob/main/.env.example#L5-L6
That's why you can only access 127.0.0.1 aka localhost. I suggest following the above documentation and build your own Docker Image for staging/production mode.
trebestie
commented
9 months ago Thanks, I'll check it out.
Il mer 3 gen 2024, 12:12 Seth Phat @.***> ha scritto:
I see, so that's why you weren't able to access it. We have these 2 env variables that need to be updated when rolling live
https://github.com/shipsaas/docking/blob/main/.env.example#L5-L6
That's why you can only access 127.0.0.1 aka localhost. I suggest following the above documentation and build your own Docker Image for staging/production mode.
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1875201719, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK2YCCFX5R7TUPA5BHXLYMU4LBAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGIYDCNZRHE . You are receiving this because you were mentioned.Message ID: @.***>
trebestie
commented
9 months ago In that page https://docking.shipsaas.tech/deployment/docker the link to Dockerfile.prod results in 404 page not found
My regards
Il giorno mer 3 gen 2024 alle ore 12:31 Diego Depaoli @.***> ha scritto:
Thanks, I'll check it out.
Il mer 3 gen 2024, 12:12 Seth Phat @.***> ha scritto:
I see, so that's why you weren't able to access it. We have these 2 env variables that need to be updated when rolling live
https://github.com/shipsaas/docking/blob/main/.env.example#L5-L6
That's why you can only access 127.0.0.1 aka localhost. I suggest following the above documentation and build your own Docker Image for staging/production mode.
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1875201719, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK2YCCFX5R7TUPA5BHXLYMU4LBAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGIYDCNZRHE . You are receiving this because you were mentioned.Message ID: @.***>
-- Diego Depaoli
sethsandaru
commented
9 months ago @trebestie it works fine for me https://docking.shipsaas.tech/deployment/docker, could you try again?
trebestie
commented
9 months ago Yes, it works, but you have to sign in to github. Is it the wanted outcome?
Il giorno mer 3 gen 2024 alle ore 13:54 Seth Phat @.***> ha scritto:
@trebestie https://github.com/trebestie it works fine for me https://docking.shipsaas.tech/deployment/docker, could you try again?
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1875329361, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK2YUHMGCLKKSHM4S4A3YMVIIPAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGMZDSMZWGE . You are receiving this because you were mentioned.Message ID: @.***>
-- Diego Depaoli
sethsandaru
commented
9 months ago No that's our public documentation, it shouldn't block you from accessing it 🤔
trebestie
commented
9 months ago The link won't work even if I'm logged in Sorry for the previous wrong answer, I supposed signing in would solve the issue without trying it
sethsandaru
commented
9 months ago @trebestie ah sorries, I added the wrong link there, correct one here https://github.com/shipsaas/docking/blob/main/.docker/prod.Dockerfile
Fixed the link on the documentation site
trebestie
commented
9 months ago Many thanks, I read the good news on the updated page. Since I'm not so familiar with docker build I'd rather wait for your upgrades than go ahead by myself Let me know if I can help you someway (translation???)
My kind regards
Il giorno gio 4 gen 2024 alle ore 02:54 Seth Phat @.***> ha scritto:
@trebestie https://github.com/trebestie ah sorries, I added the wrong link there, correct one here https://github.com/shipsaas/docking/blob/main/.docker/prod.Dockerfile
— Reply to this email directly, view it on GitHub https://github.com/shipsaas/docking/issues/27#issuecomment-1876203592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHYK2ZD2JA4OOUGAANED4DYMYDTPAVCNFSM6AAAAABBGAUDIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGIYDGNJZGI . You are receiving this because you were mentioned.Message ID: @.***>
-- Diego Depaoli
sethsandaru
commented
9 months ago sure man, thanks. Closing this oe
Hi all, i tested a DocKing installation through docker on my laptop and i could gain access to the console (localhost:8888/console). I played a little bit and it looks simple and powerful. Thank you for the nice job. My problems come inside a dedicated lxc container where the same installation won't work. Any attempt to pass over the page 192.168.XXX.YYY:8888/console crashes against an authentication failure error. Setting/unsetting password in env file doesn't change anything. On the server side.i do not see any error message What I'm wrong? How can I debug that issue?
My kind regards