Cant seem to Connect To Remote Running Container

[akash3456]

i get this message when i attempt to attach vscode insider to a running windows container

[Chuxel]

@akash3456 Windows containers are not yet supported. It would be awesome if you'd upvote #445 if you are interested in them! Closing as a duplicate.

[akash3456]

Ok thanks

…

Sent from my iPhone

On 25 May 2019, at 00:02, Chuck Lantz ***@***.***> wrote: Closed #449. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Chuxel]

Since this happens on with Linux containers, can you tell me the steps you used to create the container? Also, have you shared your local drives via Docker settings? If not, you can see an error.

[Chuxel]

Oh - and Alpine is not supported yet if you used an alpine container. See #54

[akash3456]

this is the message for linux containers:

[chrmarti]

Does setting the home folder in the Dockerfile with ENV HOME path help? (See #22 (comment).)

[akash3456]

Why do i need to do this and the container in question was created using docker run against a solr image.

[akash3456]

so what i have tried is the following:

same error occured when connecting to it remotely.

[chrmarti]

/duplicate #22

From looking at the Dockerfile for solr, ENV HOME /var/solr/data should work. This is currently a limitation.

[vscodebot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

[akash3456]

looks setting the env home to solr data dir didnt work as same error occured

[chrmarti]

@akash3456 Make sure to rebuild the container. (Either remove the container manually or go through More Actions... on the error dialog and then choose to rebuild.)

[akash3456]

I did that got the same thing. Are you able to showcase to me from your setup that this does actually work as I’m not convinced tbh

[chrmarti]

FROM solr
ENV HOME /var/solr/data

Works for me. What's the error message you get with that?

[akash3456]

#449 (comment)

Is the error message

[chrmarti]

I would expect that for the old container created without ENV HOME .... Can you delete the current container manually and then retry? (E.g., use docker ps -a to list all containers and then docker rm <container-id> to delete the old one.)

[akash3456]

so i deleted the container changed the docker file to the following :

FROM solr
ENV HOME /var/solr/data

i get the following message when remoting into it;

[chrmarti]

Maybe you're on an older version of the solr image? /var/solr exists in my version and is owned by user solr.

[akash3456]

latest image is used

[akash3456]

it seems the var/solr/data does not exist in the running container. on the solr user

[akash3456]

can you show me how yours is working at all please?
via vscode remote

[akash3456]

whats the default root user password when creating a linux container

[akash3456]

how to run commands as root in dockerfile

[akash3456]

its worked, remoed expose 8983
tanks