I fellow the instruction from official Akeneo Doc. I try to get API connection list.
php bin/console pim:oauth-server:list-clients --env=prod
Every time I run this command in terminal, it throws error.
Could not open input file: bin/console
I tried for both version 1.7 and 2.0. It's still same.
Do i need to open terminal in certain folder to run?
Akeneo Server is on docker.
First I find Id of my container (for me, it's Akeneo)
docker container ls
my Akeneo Id on docker is
"0de07xxxxxxx"
I exac my container my this command
docker exec -it "0de07xxxxxxx" bash
and I find my path folder by find command.
find / -name app
Now i can run php command to get api connection list.
and yeah i do need to open terminal in akeneo folder to run php command lines.
Related
I'm trying to reproduce the code from this github：enter link description here. The purpose of this project is to use the GPU to perform some similarity search. Based on the instruction of the README file, I can now open the search server website inside the docker now. But I have tried many ways to try to open this server URL from an external browser, but all failed, can anyone help? Thanks!
Here is how I opened my server URL inside the Docker:
Download Docker Desktop.
Pull the images:
docker pull klorton/gpusimilarity:latest
From the docker directory(The docker file is inside the github), build:
docker build -t gpusim:internal .
Build a fingerprint file (Database), change PATH/TO/SMIGZ_DIR to your own path to the smi.gz file, change INPUT to your own smi.gz file.
docker run -v /PATH/TO/SMIGZ_DIR:/data -it gpusim python3 \
/gpusimilarity/bld/python/gpusim_createdb.py /data/INPUT.smi.gz \
/data/OUTPUT.fsim
Start a gpusimilarity server interactively, change /path/to/fsim/files to your own path to the fsim file.
docker run --net=host -v /path/to/fsim/files:/mnt/fsim -it \
klorton/gpusimilarity:latest python3 /gpusimilarity/bld/python/gpusim_server.py \
/mnt/fsim/OUTPUT.fsim --port 8080 --http_interface
The server will say "Ready for search" at this moment. Something like this:
enter image description here
7.The server is running now. In the README file, the author said that we can just use the following link: http://localhost:8080 to open it. But I failed by doing this.
Then I tried to open the URL inside the Docker, install w3m first.
apt-get install -y w3m
Open the URL inside the Docker:
w3m http://localhost:8080
It shows like this:
enter image description here
Can someone tell me how to open this URL outside of Docker? Thanks a lot!
I have tried many of the methods available on Google, But most of them don't work...
I solved this. Just Downgrade docker and run the same process by linux.
I am following official Hyperledger Fabric documentation(Build your first network). When executing docker exec -it cli bash, it is not being executed. There is no response. I cannot use peer command.
docker exec -it cli bash, output:
root#e45419781222:/opt/gopath/src/github.com/hyperledger/fabric/peer#
I cannot enter further commands and it doesn't show any errors. And when I try to use peer command from another terminal, it throws peer command not found.
I think it is not connected to cli container.
I am just starting out with hyperledger. I cannot identify the error and it seems there is no resources regarding this issue.
I expect to connect to the cli container.
Try this command.
docker exec -it cli /bin/bash
Sorry, very dumb mistake even for linux and fabric noobie. I realized you have to write command after "root#e45419781222:/opt/gopath/src/github.com/hyperledger/fabric/peer#". I thought this was end of the execution. And peer command works form this rather than opening new terminal.
I have the following basic Dockerfile:
FROM mcr.microsoft.com/windows/servercore:1903
CMD echo Hello World!
When I run the command:
docker build -t latest . or docker build .
My terminal hangs forever and it seems like nothing is being done.
However, if I run:
docker pull mcr.microsoft.com/windows/servercore:1903
I can pull the image from the repository.
I'm not sure what I'm doing wrong, or how to fix it. The build command doesn't seem to have a verbose option, and I need a docker container running Windows.
I'm using Docker in Windows 10 Pro and its configured to use Windows containers.
Check which directory do you execute your commands from. You shall be executing them from directory where DOCKERFILE is located and nothing else. If you execute say from root of C drive or any other location with big number of files then docker as a first step will try to zip all of them up and then send to a builder and hence delays.
I am trying to get the Superset running on ubuntu server. I have referenced the steps from Superset page as below:
git clone https://github.com/apache/incubator-superset/
cd incubator-superset/contrib/docker
# prefix with SUPERSET_LOAD_EXAMPLES=yes to load examples:
docker-compose run --rm superset ./docker-init.sh
# you can run this command everytime you need to start superset now:
docker-compose up
I have fixed the initial issues around right version of docker-compose and postgress address bind issue on port 5432. So after fixing those my docker compose run command
docker-compose run --rm superset ./docker-init.sh
works fine and it asks me to set up a user name and password.
Finally to get the container running I run the final command
docker-compose up.
On my mac, it would run redis, postrgre container and then give me a localhost:8088 for me to get access to Superset UI with login info.
However on Ubuntu, when I run that, I first get this:
So looks it is running redis and postgres containers fine.
But then it is giving me Permission denied errors to create some mkdir directory.
Pls note I am running it as root user.
Also, my docker compose version is fine with 1.23.2 and my docker along with docker-compose is installed under
/usr/bin/docker and not /usr/local/bin/docker.
But I think that shouldn't be an issue.
Any help where it is going wrong and how can I fix it?
Thanks
Edit:
Ok I looked at the same issue mentioned on Github. And used a suggestion of using it only for Production and not development in docker-compose.yml file.
It seems to not throw the same error now when I do
docker-compose up.
However when I open localhost:8088 it does not connect to the UI.
try this:
mkdir ../../assets
chmod -R 777 ../../superset/assets/
as set in docker-compose.yml#L64, it is using ../../superset as volume when in develop. However the container does not have any permission in the host so the solution is to make a directory by yourself and grant the necessary permissions on to it.
I am using Docker with Kitematic and I have installed an image of Linux with Magento 2 on it.
It all works well, but Magento 2 requires that I run terminal commands for several things. How do I do this?
I know where the terminal is and there's Docker CLU, but when I go to the actual Magento directory, there's only the app but no bin/magento? So how does this work, or, in other words, where do I run the root commands from?
This has already been asked and answered. Just run
docker exec -it <container_id_or_name> /bin/bash
Check the link below.
How do I run a command on an already existing Docker container?